Subj : Re: Events - Only Hourly and Semaphore run
To   : g00r00
From : Chris Hizny
Date : Sat Feb 05 2022 05:41 pm

 g0>  CH> + 2022.02.04 19:42:08  EVENT Running event: Nightly Maintenance
 g0>  CH> + 2022.02.04 19:42:08  EVENT Cmd: /mystic/proof.sh
 g0>  CH> + 2022.02.04 19:42:08  EVENT Res: 0
 g0> 
 g0> I will make a test to see if I can reproduce a similar issue on my Linux
 g0> machine here, but the only thing that comes to mind is maybe something
 g0> access related?
 g0> 
 g0> Your script isn't going to run properly if whatever runs it doesn't have
 g0> access to echo to a log file in the logs directory.  It seems Mystic is
 g0> trying to run it based on the logs and the OS is returning a 0.  That
 g0> implies that it does actually run.
 
Well, in this case, you're looking at the hourly run, which *does* work.  That's important.  Hourly is fine.  I can run anything hourly.  The problem is if I change this from hourly to a shell or interval event type, it will not run, and will not create a log entry like the above.

That's why I am confused.

As for log permissions, they seem fine:

-rw-r--r--  1 mystic mystic      46 Feb  5 11:10 errors.log
-rw-r--r--  1 mystic mystic  376984 Feb  5 17:09 mis.log
-rw-r--r--  1 mystic mystic  261005 Feb  4 23:20 mutil.20220204.log
-rw-r--r--  1 mystic mystic   20434 Feb  5 01:30 mutil.20220205.log
-rw-r--r--  1 mystic mystic 1830926 Feb  5 17:35 mutil.log
-rw-r--r--  1 mystic mystic    6104 Feb  5 17:31 node1.log
-rw-r--r--  1 mystic mystic     710 Feb  5 09:27 node2.log
-rw-r--r--  1 mystic mystic     231 Feb  4 13:03 node3.log
-rw-r--r--  1 mystic mystic  576488 Feb  5 17:35 poll.log
-rw-r--r--  1 mystic mystic   52104 Feb  5 17:10 qwkpoll.log
drwxrwxr-x  2 mystic mystic    4096 Sep 28 03:18 tempmis

Thanks for the explanation of the BBS event type.

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
 * Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (1:218/860)

.