open https://gitlab.synchro.net/main/sbbs/-/issues/1086

My system logs via syslog, but apparently events *also* lot to `logs/events.log` now and that file just grows forever.

The first entry in that file is from 2025-10-19, and it's 1.3GB.
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/1086#note_8459

It should be rotating per whatever policy you have configured in SCFG->System->Advanced->Maximum Log File Size.
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/1086#note_8462

That is unlimited as there's no rotate by date option.

As an aside, events.log isn't mentioned in the Maximum Log File Size scfg help.

It seems that setting EventLogLevel to zero will suppress this redundant file, so this can be closed if you have no plans on changing the behaviour.
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/1086#note_8472

The file in question does rotate (does not "grow forever"), so I'm not clear what behavior I would change.

We could add a rotate by date option I guess, but nobody's ever asked for it. --- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/1086#note_8478

I mean, this is a new fully redundant log file filled with entries from the BBS working correctly.

While you can configure it to rotate based on size, that configuration is shared with log files that do indicate a potential issue and do not grow nearly as fast (and only some of them are redundant).

For my purposes, simply effectively disabling it by setting `EventLogLevel` to 0 is fine, but if it's expected to be in general use (apparently there's a QWK stats thing the requires it?), having a separate config for it could make sense.
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 27 Feb 2026, Deuc¨ said the following...

https://gitlab.synchro.net/main/sbbs/-/issues/1086#note_8478
I mean, this is a new fully redundant log file filled with entries from the BBS working correctly.

While you can configure it to rotate based on size, that configuration is shared with log files that do indicate a potential issue and do not grow nearly as fast (and only some of them are redundant).

For my purposes, simply effectively disabling it by setting `EventLogLevel` to 0 is fine, but if it's expected to be in general use (apparently there's a QWK stats thing the requires it?), having a
separate config for it could make sense.

why not just include and use a copy of the linux logrotate utility?

there's also a workalike for windows that claims 91% feature parity:

https://github.com/plecos/logrotatewin

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
# Origin: cold fusion - cfbbs.net - grand rapids, mi
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: events.log file does not rotate
By: fusion to Deuc¨ on Sat Feb 28 2026 04:41 pm

why not just include and use a copy of the linux logrotate utility?

Because I already manage the logs via syslog.
---
þ Synchronet þ The future of BBSing
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)