TID: Mystic BBS 1.12 A48   
   MSGID: 1:129/215 b1fa8b21   
   REPLY: 1:218/860 a7f23e4c   
   TZUTC: -0500   
    CH> + 2022.02.04 19:42:08  EVENT Running event: Nightly Maintenance   
    CH> + 2022.02.04 19:42:08  EVENT Cmd: /mystic/proof.sh   
    CH> + 2022.02.04 19:42:08  EVENT Res: 0   
      
   I will make a test to see if I can reproduce a similar issue on my Linux   
   machine here, but the only thing that comes to mind is maybe something access   
   related?   
      
   Your script isn't going to run properly if whatever runs it doesn't have   
   access to echo to a log file in the logs directory.  It seems Mystic is trying   
   to run it based on the logs and the OS is returning a 0.  That implies that it   
   does actually run.   
      
    CH> My question is, what would cause this?  Also what is a BBS event type   
    CH> (these are not described in the Mystic Wiki).   
      
   There is no section for events written yet but I should probably put that on   
   my TO-DO list.  Instead they are listed in the WHATSNEW.  I searched for   
   "event type" on the Wiki and found this:   
      
    TYPE4: BBS   
    ==========   
      
    This event type is not actually executed by MIS itself, and is similar to   
    what you might have found in old DOS-based BBS software.  The purpose for   
    this event is to provide an option to force users to log off the BBS if   
    you want them to.   
      
    Like the scheduled Shell event, a BBS type event can be scheduled at a   
    certain hour/min and one or more days of the week.  In addition to the   
    time/day scheduling there are some other options:   
      
          Node: This defines the node number for which the event will execute.   
                If you keep the node number at 0, it will be applied to all   
                users on all nodes.   
      
       Warning: This determins the time before the event to notify the user   
                of the upcoming event.  This can be set to 0 to never warn them,   
                or (for example) 10 to give them a message that they will be   
                required to logoff in 10 minutes.   
      
    When this event time hits, the user will be logged off of the BBS if they   
    have not already logged off on their own.   
      
   ... A SQL query walks into a bar and sees two tables. Asks: 'Can I join you?'   
      
   --- Mystic BBS v1.12 A48 2022/02/03 (Windows/64)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 616 123/10   
   SEEN-BY: 123/120 131 129/215 305 330 331 153/7715 154/10 30 40 50   
   SEEN-BY: 154/700 203/0 218/840 220/70 90 221/6 226/17 18 30 100 227/114   
   SEEN-BY: 227/201 229/110 206 307 310 317 400 424 426 428 452 550 664   
   SEEN-BY: 229/700 240/5832 250/5 8 266/512 267/800 280/464 282/1038   
   SEEN-BY: 292/854 298/25 301/1 305/2 3 317/3 320/219 322/757 342/200   
   SEEN-BY: 396/45 460/58 633/280 712/848 770/1 2320/105 3634/12   
   PATH: 129/215 154/10 770/1 317/3 229/426