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

I sometimes use the ;log command while logged in as the Sysop, to see
what previous callers that day may have been up to.

For example, me logging in to retrieve a QWK packet:

--------------------------------------------------------------------
@ 08:43p Fri Nov 21 2025 Node 1
@+ Telnet moria [192.168.254.50]
++ (0001) Gamgee Logon 0 - 3
X- running external user event: BullsEye! Bulletins
;LOG,QD
z 135633 115200 bps 135633 cps 0 errors 0 1024 /sbbs/node1/TEMP/PALANT
IR.qwk -1
D- downloaded QWK packet
Q,X
X- running external program: Global Backgammon
X- running external program: Legend of the Red Dragon
E,O
@- 09:04p T: 21 R:112 P: 0 E: 0 F: 0 U: 0K 0 D: 0K 0 ---------------------------------------------------------------------

I'm used to seeing only an entry for callers doing things like that...

But since that last upgrade, I'm seeing things like this in the log:

---------------------------------------------------------------------

@ 02:18a Sat Nov 22 2025 Node 1
@+ Telnet vert.synchro.net [71.95.196.34]
@- 02:18a T: 15 sec

@ 03:21a Sat Nov 22 2025 Node 1
@+ Telnet 23-31-96-97-static.hfc.comcastbusiness.net [23.31.96.97]
@- 03:21a T: 7 sec

@ 03:53a Sat Nov 22 2025 Node 1
@+ Telnet n49-193-126-165.sun22.vic.optusnet.com.au [49.193.126.165]
@- 03:54a T: 24 sec ---------------------------------------------------------------------

Those are obvious bot/timeout connects, but they never used to show up
in the log that way. Is anyone else noticing this, and/or have any idea
why it's just started happening?

Digialman - you made this comment on my post on DoveNet (quoted above) which may help you remember where to start/look at this:

I don't know for sure, but it's probably an unintentional side-effect of this change:
https://gitlab.synchro.net/main/sbbs/-/commit/f189dc3fcea244e064992a9fa8c433b

Thank you for checking into this, it's greatly appreciated!
--- SBBSecho 3.32-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)