TZUTC: -0800
MSGID: 58906.sync_sys@1:103/705 2d888e14
REPLY: 58905.sync_sys@1:103/705 2d888243
PID: Synchronet 3.21a-Linux master/ec8f7009f Nov 15 2025 GCC 12.2.0
TID: SBBSecho 3.32-Linux master/ec8f7009f Nov 15 2025 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: CP437 2
FORMAT: flowed
NOTE: FSEditor.js v1.105
  Re: Changes to ;log command?
  By: Gamgee to All on Sat Nov 22 2025 07:00 pm

 > Hi all,
 >
 > Noticed something today that seems to be an unexpected change, after a
 > system (git) update a couple of days ago.
 >
 > 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?

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

If you create an issue on gitlab, I'll be more likely to remember to look
deeper into/fix it.
-- 
                                            digital man (rob)

This Is Spinal Tap quote #37:
David St. Hubbins: We are Spinal Tap from the UK - you must be the USA!
Norco, CA WX: 61.2øF, 62.0% humidity, 1 mph SSW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.32-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 13/0 102/401 103/1 13 17 705 105/81 106/201 124/5016
SEEN-BY: 128/187 129/14 153/7715 154/110 214/22 218/0 1 215 601 610
SEEN-BY: 218/700 840 860 880 226/30 227/114 229/110 112 206 317 400
SEEN-BY: 229/426 428 470 700 705 266/512 280/464 291/111 301/1 320/219
SEEN-BY: 322/757 342/200 396/45 460/58 633/280 712/848 902/26 5075/35
PATH: 103/705 218/700 229/426