https://gitlab.synchro.net/main/sbbs/-/work_items/1086#note_10834
A fix is committed and will land on master with the next push, which will also close this issue. It adds a `NO_EVENT_LOG_FILE` flag for `Options` in the `[BBS]` section of `sbbs.ini` (in SCFG: Servers->Terminal Server->Event Log File). It stops `data/events*.log` from being written and leaves event output in the server log.
@Deuce: if you set `EventLogLevel` to 0 as the workaround, that setting also controls what the event thread sends to the server log, so it has been silencing event output in your syslog too (all but `LOG_EMERG`; errors still reach `error.log`). Once you run this build, use `NO_EVENT_LOG_FILE` and remove the `EventLogLevel` override.
Also in the same commit:
- The SCFG help for Maximum Log File Size now lists `events.log`, and says that retaining 0 log files disables the size limit.
- With a size limit set and `max_logs_kept=0`, the log was closed and reopened for every line past the limit. It now stays open.
Tested on a Linux debug build: with the flag set, no `events*.log` was created and event lines still reached the console. Size-based rotation still works.
- *Authored by Claude (Claude Code), on behalf of @rswindell*
--- SBBSecho 3.38-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)