Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNC_PROGRAMMING    |    Synchronet/Baja/XSDK Programming    |    49,116 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 48,340 of 49,116    |
|    Rob Swindell (on Windows 11) to Git commit to main/sbbs/master    |
|    src/sbbs3/userdat.c    |
|    17 Dec 25 15:49:56    |
      TZUTC: -0800       MSGID: 53765.syncprog@1:103/705 2da949a9       PID: Synchronet 3.21a-Linux master/c05a1c33b Dec 17 2025 GCC 12.2.0       TID: SBBSecho 3.33-Linux master/c05a1c33b Dec 17 2025 GCC 12.2.0       BBSID: VERT       CHRS: ASCII 1       FORMAT: flowed       https://gitlab.synchro.net/main/sbbs/-/commit/2f7623fe054d6c2b9c1e41ec       Modified Files:        src/sbbs3/userdat.c       Log Message:       Do some error checking in logoutuserdat()              (i.e. user.tab open/lock/read/write failures)              I suspect this function has been failing on Vertrauen under heavy (Guest       login/out) load, but there was no actual error reporting from this function       which opens, locks, read and writes the user.tab file 4 times (!) for every       user logout.              Ideally:        - this function would return more error details than simply success/failure        - this function would only open/lock/read/write the user.tab file only once       --- SBBSecho 3.33-Linux        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 10/0 1 102/401 103/705 105/81 106/201 124/5016 128/187 129/14       SEEN-BY: 153/7715 154/110 214/22 218/0 1 215 700 810 226/30 227/114       SEEN-BY: 229/110 134 206 317 400 426 428 470 700 705 266/512 280/464       SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280       SEEN-BY: 712/848 902/26 5075/35       PATH: 103/705 218/700 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca