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.<code>.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.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/460b5f93b2dd5eca7bfee64b
Modified Files:
src/sbbs3/main.cpp sbbs.h
Log Message:
Log the total amount of user and mail data backed-up daily (in bytes)

This was done previous, file by file, at debug log level, in exact bytes.
That detail is still logged, however the "DAILY: Backing-up ..." log messages are now debug (instead of info) level messages and the total number of bytes (estimated) is now logged at info-level after the backup has completed with "DAILY: Backed-up ..." messages.

This allows easier tracking of the mail and user base growth over time through log analysis (if the sysop has auto-backups enabled).

With possible use of "Fast Allocation" (instead of Self-packing) for the
mail base, it is important that a sysop should be able to easily track the growth rate over time to determine the (necessary) packing interval.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net