Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 48808  |
|  Rob Swindell (on Windows 11) to Git commit to main/sbbs/master  |
|  src/sbbs3/chk_ar.cpp client.h mailsrvr.c  |
|  21 Jan 26 19:33:52  |
 TZUTC: -0800 MSGID: 54242.syncprog@1:103/705 2dd7a482 PID: Synchronet 3.21b-Linux master/11183ff91 Jan 21 2026 GCC 12.2.0 TID: SBBSecho 3.35-Linux master/5c73d262c Jan 21 2026 GCC 12.2.0 BBSID: VERT CHRS: ASCII 1 FORMAT: flowed https://gitlab.synchro.net/main/sbbs/-/commit/5c73d262cc4683798b8cae66 Modified Files: src/sbbs3/chk_ar.cpp client.h mailsrvr.cpp main.cpp sbbsdefs.h userdat.c userdat.h Log Message: Treat user numbers a 32-bit signed integers, everywhere we had mix of signed/unsigned and 16 and 32-bit integer representations of the user number. I somehow ended up with a 4GB (4294967296 byte) user.tab file today and don't have an exact smoking gun but the conversions (mainly in userdat.c) between unsigned 16-bit and signed 32-bit representation of the user number had me suspicious. Perform some userbase data file and index file sanity checking upon startup of the terminal server thread and fail with critical error if anything seems amiss (indication of corruption). --- SBBSecho 3.35-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 1/19 100 16/0 19/37 103/705 105/81 106/201 123/130 124/5016 SEEN-BY: 128/187 129/14 142/104 153/757 7715 154/10 30 110 203/0 218/700 SEEN-BY: 221/0 1 6 226/30 227/114 229/110 134 206 317 400 426 428 SEEN-BY: 229/470 700 705 240/1120 5832 263/1 266/512 280/464 5003 SEEN-BY: 280/5006 291/111 292/8125 301/1 320/119 219 319 2119 322/757 SEEN-BY: 322/762 341/66 234 342/200 396/45 423/81 120 460/58 633/280 SEEN-BY: 712/848 770/1 902/26 5020/400 5075/35 PATH: 103/705 280/464 221/1 320/219 229/426 |
[ << oldest | < older | list | newer > | newest >> ]