home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.bbs.mystic      Mystic Sysops are mystical nerds...      11,847 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 10,514 of 11,847   
   g00r00 to All   
   Re: Events - Only Hourly and Semaphore r   
   05 Feb 22 10:45:23   
   
   From: nospam.g00r00@f215.n129.z1.fidonet.org   
      
    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?'   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca