Hi All,

I don't know if this was just a fluke, or what. I have my 'Poll Echomail'
even set to run at 1 hour intervals. I also have my 'Nightly Events' set to
run at 4am every day.

I noticed last night, that my maintenance event didn't run. Looking at the logs, I noticed at 4am my system was running an echomail poll, which includes scanning for outbound message, fidopoll send, and tossing any new messages. This poll started at 04:00:13 and ran until 04:03:13. After that time, it seemed to continue with normal operation, without running the 4am shell event.

Is there a way to force a shell event to run, even if it is after the time it was scheduled for? I've only seen it happen twice so far, so it's not a major issue.

Thanks in advance.


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A33 (Windows/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Set it to run at4:30 am. It will never have an echomail run then? :)

On 09:08 26/05 , Black Panther wrote:

Hi All,

I don't know if this was just a fluke, or what. I have my 'Poll Echomail' >even set to run at 1 hour intervals. I also have my 'Nightly Events' set to >run at 4am every day.

I noticed last night, that my maintenance event didn't run. Looking at the >logs, I noticed at 4am my system was running an echomail poll, which includes >scanning for outbound message, fidopoll send, and tossing any new messages. >This poll started at 04:00:13 and ran until 04:03:13. After that time, it >seemed to continue with normal operation, without running the 4am shell event.

Is there a way to force a shell event to run, even if it is after the time it >was scheduled for? I've only seen it happen twice so far, so it's not a major >issue.

Thanks in advance.

---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A33 (Windows/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

On 05/26/17, Black Panther pondered and said...

I noticed last night, that my maintenance event didn't run. Looking at
the logs, I noticed at 4am my system was running an echomail poll, which includes scanning for outbound message, fidopoll send, and tossing any
new messages. This poll started at 04:00:13 and ran until 04:03:13.
After that time, it seemed to continue with normal operation, without running the 4am shell event.

I have seen this also when I had a number of events set to run close to each other and if those events took a long time to execute individually it could lead to others not running.

My take out from this is that for an event to fire another one must not be running at the same time. You need mystic to recognize the event has ended
and the process result code of 0 has been returned before the event focus is returned to act on another event.

I'd suggest there needs to be a window of flexibility built in to each event that perhaps is sysop adjustable. So set a time in minutes that the event may still run if the desired execution time has already past. This would largely solve the problem I think.

For now the best thing it to look at the time it takes to run some events - likely nightly maintenance - and ensure you don't try to run another one
during that execution time.

g00r00 may wish to comment on this also but that's my interpretation of it :)

Best, Paul

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 05/27/17, Avon said the following...

My take out from this is that for an event to fire another one must not
be running at the same time. You need mystic to recognize the event has ended and the process result code of 0 has been returned before the
event focus is returned to act on another event.

Thanks for the reply. What I've done, instead of having the echomail poll set to run at 1 hour intervals, is change it to run hourly at :45.

I hope this will keep this from happening. I just assumed that if an event
was running at 4am, the 4am event would cue up to run after.


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A33 (Windows/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Hey g00r00 =)

I have a question about Mystic Events... are they able to run menu
commands and/or mpx/mpy scripts also or are they only able to run shell scripts?

Thanks in advance for your help.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÄ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ

--- Mystic BBS v1.12 A43 2019/02/10 (Linux/64)
* Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)

On 25 Feb 2019, MeaTLoTioN said the following...

Hey g00r00 =)

I have a question about Mystic Events... are they able to run menu commands and/or mpx/mpy scripts also or are they only able to run shell scripts?

I can answer that. They can run anything you can run on a command line, and there are mystic command line options you can use which can be found in the mystic.txt in your DOCS directory. I think that doc is outdated, though.

--- Mystic BBS v1.12 A43 2019/02/23 (Raspberry Pi/32)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

I have a question about Mystic Events... are they able to run menu commands and/or mpx/mpy scripts also or are they only able to run shell scripts?

You can run MPL and Python scripts from command line, so you can have an
event run either of them using the command line. You do have to supply a
user though to run the script as.

mystic -uScripbot -pPassword -Xmpl
mystic -uScripbot -pPassword -Ypython

--- Mystic BBS v1.12 A43 2019/02/17 (Linux/64)
* Origin: Sector 7 (21:1/108)