TZUTC: -0800
MSGID: 53446.syncprog@1:103/705 2d6facf3
PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0
TID: SBBSecho 3.31-Linux master/b0c0913d9 Nov 03 2025 GCC 12.2.0
BBSID: VERT
CHRS: ASCII 1
FORMAT: flowed
https://gitlab.synchro.net/main/sbbs/-/commit/1372d896d8238236c7eec79e
Modified Files:
	src/sbbs3/main.cpp sbbs.h xtrn_sec.cpp
Log Message:
Don't let user run external program that's executing its assigned event

... using 0-byte semfile: data/event..running

The second part of fix for issue #998

Kind of abusing/reusing a node status string for the error message displayed
to a user that tries to run the program while the event is running. Might want
to address that (support an error display file or other text.dat string) later.

Background events don't work for this (since we never know if/when they're
finished executing).

If an event is configured to run exclusive, but on "any node" and you run
multiple instances of sbbs (using the same data dir), then this isn't going
to work for you since the event thread deletes any stale semfiles when it
starts up.
--- SBBSecho 3.31-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 102/401 103/1 705 105/81 106/201 124/5016 128/187
SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 610 700 810 226/30
SEEN-BY: 227/114 229/110 206 317 400 426 428 470 700 705 266/512 280/464
SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280
SEEN-BY: 712/848 902/26 5075/35
PATH: 103/705 218/700 229/426