• src/sbbs3/main.cpp sbbs.h

    From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Tuesday, April 09, 2024 18:03:01
    https://gitlab.synchro.net/main/sbbs/-/commit/221507a8d36e31306b0e9a6d
    Modified Files:
    src/sbbs3/main.cpp sbbs.h
    Log Message:
    Reduce the Terminal Server thread outcom timeout from 80 seconds to 800 ms

    Since the Terminal Server is a single thread, let's not block for long
    periods of time trying to send bytes to a client (e.g. send the badip.msg
    file contents to a client with a blocked IP address), effectively DoSing the terminal server.

    This should address the problem reported via IRC:
    <theviper4> ³Apr 9 15:38:11 viper-bbs synchronet: term Terminal Server timeout(outcom) 0000 0000
    <theviper4> ³Apr 9 15:38:35 viper-bbs synchronet: term Terminal Server !ERROR 110 sending on socket 39
    <theviper4> ³Apr 9 15:38:35 viper-bbs synchronet: term Terminal Server !ERROR 32 sending on socket 39
    <theviper4> ³Apr 9 15:38:35 viper-bbs synchronet: term Terminal Server !ERROR 32 sending on socket 39
    <theviper4> ³Apr 9 15:38:36 viper-bbs synchronet: term 0039 Telnet !CLIENT BLOCKED in ip.can: 117.95.153.33

    Also, make the outcom timeout error message more helpful (e.g. include the
    sock descriptor of the client) and don't use the old rioctl() function
    here any more.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Monday, January 19, 2026 01:20:09
    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