TID: Mystic BBS 1.12 A47   
   MSGID: 1:218/860 a7f23e4c   
   TZUTC: 0000   
   v1.12 A47 (2021/12/24), but this also was problematic on A46.   
      
   Hourly jobs (mainly polls) run fine.   
   Semaphore-based events run fine.   
      
   Shell and Interval do not.   
      
   My intent was to run nightly maintenance:   
      
    /mystic/mutil maint.ini   
      
   This command works fine if I run it manually from the command line.  My logs   
   show nothing, other than no indication that this event ran.  There are no   
   error messages of any sort.   
      
   Some helpful folks on fsxNet suggested I play with the paths some.  This did   
   not make any difference.  I thought, okay, maybe restart mis after a change,   
   as I don't know when that is read and compiled into event file (event.dat) but   
   that made no difference either.   
      
   I tried the following:   
      
    ./mutil maint.ini   
    ./mutil ./maint.ini   
    /mystic/mutil /mystic/maint.ini   
    /mystic/mutil maint.ini   
       
   Same behavior.  Tried switching to interval, then back to shell for each.   
      
   So then I said, forget mutil for now.  I created a shell script which simply   
   does this:   
      
   #!/bin/bash   
   rightnow=$(date)   
   echo "${rightnow}" >> /mystic/logs/MAINT_IS_RUNNING_HUZZAH   
      
   Which runs fine from the command line.   
      
   Same issue.  So it wasn't anything with mutil so far as I can tell.   
      
   What I did learn was that if I schedule this to run hourly, it runs fine.  But   
   that is the only event type that runs.  Since I know this runs fine, I know   
   this command/path works:   
      
    /mystic/proof.sh   
      
   But this will not run as a shell or interval event.   
      
   My question is, what would cause this?  Also what is a BBS event type (these   
   are not described in the Mystic Wiki).   
      
   The hourly events show up in the logs.  If I set it to shell, it does not.  I   
   have the logging level set to MAX currently.   
      
   + 2022.02.04 19:42:08  EVENT Running event: Nightly Maintenance   
   + 2022.02.04 19:42:08  EVENT Cmd: /mystic/proof.sh   
   + 2022.02.04 19:42:08  EVENT Res: 0   
      
   I have taken a screenshot of the event configuration here just in case I am   
   doing something obviously wrong:   
      
   https://i.imgur.com/IRRuyOq.png   
      
   --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)   
    * Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (1:218/860)   
   SEEN-BY: 1/123 10/0 1 15/0 90/1 102/401 103/1 705 105/81 106/201 114/705   
   SEEN-BY: 120/340 123/120 131 129/305 330 331 153/7715 154/10 214/22   
   SEEN-BY: 218/0 1 410 530 700 720 802 810 830 840 850 860 870 880 220/70   
   SEEN-BY: 221/6 226/17 30 100 227/114 229/110 206 307 317 400 424 426   
   SEEN-BY: 229/428 452 550 664 700 240/5832 250/5 8 261/38 266/512 267/800   
   SEEN-BY: 282/1038 292/854 298/25 301/1 305/2 3 317/3 320/219 322/757   
   SEEN-BY: 342/200 396/45 460/58 633/280 712/848 770/1   
   PATH: 218/860 700 840 770/1 317/3 229/426