_  _    __    ___  __    ___  _____  _  _
 ( \( )  /__\  / __)(  )  / __)(  _  )( \( )
  )  (  /(__)\( (__  )(__( (__  )(_)(  )  (
 (_)\_)(__)(__)\___)(____)\___)(_____)(_)\_)

The History of Hacking  ·  May 31 – June 2, 2026  ·  Carolina Beach, NC

Connect from your terminal: telnet naclconbbs.net 23  |  ssh naclconbbs.net -p 2222

  1. Forum
  2. DOVE-Net
  3. Synchronet Programming

  • src/sbbs3/ftpsrvr.cpp mailsrvr.cpp main.cpp services.cpp websrvr.cpp

    From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Sat May 2 20:14:22 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/74d228e477cbdd68551d2a4d
    Modified Files:
    src/sbbs3/ftpsrvr.cpp mailsrvr.cpp main.cpp services.cpp websrvr.cpp Log Message:
    sbbs3 servers: demote zero-removal clear log to LOG_DEBUG

    The five servers share a single login_attempt_list. When a generic
    ctrl/clear semfile is touched (or a host-level MQTT clear topic
    fires), every server independently fans out and tries to clear the
    same shared list. The first to grab the list lock removes the
    matching entries; the others find them already gone and would log
    "Cleared 0 login attempt(s) for IP X" at LOG_INFO -- four redundant
    info-level lines per signal.

    Drop those zero-count messages to LOG_DEBUG so a real clear stays
    visible at INFO while the runner-up servers stay quiet at default
    log levels. The list-lock already serializes the mutations, so
    correctness is unchanged -- this is purely log-noise reduction.

    Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

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