TZUTC: -0700   
   MSGID: 58787.sync_sys@1:103/705 2d6ba72d   
   PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0   
   TID: SBBSecho 3.30-Linux master/3b5271993 Oct 31 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/issues/998#note_7825   
      
   Making it so that a specific timed event (or set of events) won't run while a   
   user is running a specified external program is pretty easy to do since the   
   node.dab tracks what external programs are being run by any nodes at any given   
   time.   
      
   However, preventing a user from running an external program because a timed   
   event is running is a bit trickier because there is no common data file that   
   all nodes can just look at to determine if a timed event is being executed at   
   that moment. I suppose one could be added.   
      
   However, normally this situation is handled by making the timed event in   
   question run "exclusively", which means all nodes must be in an offline or   
   limbo state before the timed event will run, and the nodes will be   
   automatically returned to WFC/listening state when the event is complete. Is   
   there a reason that's not a solution for this case?   
   --- SBBSecho 3.30-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 13 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 601 610 700 840   
   SEEN-BY: 218/860 880 226/30 227/114 229/110 112 206 317 400 426 428   
   SEEN-BY: 229/470 700 705 266/512 280/464 291/111 301/1 320/219 322/757   
   SEEN-BY: 342/200 396/45 460/58 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426