Subj : External Program mutually exclusive groups
To   : GitLab note in main/sbbs
From : Rob Swindell
Date : Fri Oct 31 2025 21:24:42

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)

.