• ctrl/sbbs.ini docs/v322_new.md src/sbbs3/logfile.cpp main.cpp src/sbbs

    From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Sun Nov 8 17:22:16 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/75463dc5d2fbe6a79d522659
    Modified Files:
    ctrl/sbbs.ini docs/v322_new.md src/sbbs3/logfile.cpp main.cpp src/sbbs3/scfg/scfgindex.h scfgsrvr.c scfgsys.c src/sbbs3/startup.h
    Log Message:
    Add NO_EVENT_LOG_FILE option to stop writing data/events*.log

    The event thread's log file duplicates what the server log already holds
    on systems that log to syslog, and it can only be bounded by the size
    limit it shares with the much smaller error logs. Setting EventLogLevel
    to 0 kept the file from being written, but that level also gates the
    server log, so it silenced event output there as well.

    The new Terminal Server option (SCFG: Event Log File) stops the file
    only. Nothing in the stock install reads it.

    With a size limit but max_logs_kept=0, fopenlog() never rotates, yet fprintlog() still closed the file at the limit, so every further line
    paid for a close and reopen. Close only when rotation can happen. SCFG
    already displays that combination as Unlimited; its help now says so,
    and also lists events.log among the size-limited logs.

    Fixes #1086

    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net