• max concurrent connections limit applied before completing logon

    From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Sat Sep 27 15:15:18 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/979#note_7670

    The issue I see isn't really a SYSOP or exemption issue, it's that the successful login isn't "registered" (added to the `current_logins` list in `main.cpp`) until _after_ the logon process is complete and the checking/reading of waiting mail occurs during (not after) the logon process.
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Sat Sep 27 19:34:54 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/979#note_7672

    Also, assuming the value is configurable, I would suggest that if you like being able to do that, your users potentially would as well, so it makes sense to use the same value for the Sysop as regular users.
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Sat Sep 27 19:35:51 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/979#note_7673

    I would have thought that once the username and password were authenticated then that would be successful login?
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Sat Sep 27 22:04:06 2025
    close https://gitlab.synchro.net/main/sbbs/-/issues/979
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)