home bbs files messages ]

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,646 of 49,116   
   Rob Swindell (on Windows 11) to Git commit to main/sbbs/master   
   src/sbbs3/logon.cpp   
   11 Jan 26 03:40:05   
   
   TZUTC: -0800   
   MSGID: 54077.syncprog@1:103/705 2dc99552   
   PID: Synchronet 3.21b-Linux master/177a369d2 Jan 04 2026 GCC 12.2.0   
   TID: SBBSecho 3.34-Linux master/f825a2189 Jan 11 2026 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/commit/bcd74f4f124ba2f12f1289dc   
   Modified Files:   
   	src/sbbs3/logon.cpp   
   Log Message:   
   Fix race condition with concurrent instances updating stats files (?sts.*)   
      
   If you run multiple instances of sbbs sharing the same data files (I know you   
   don't) *and* you have more than one instance running the terminal server timed   
   events thread with "New day events" enabled (the default), you ran the risk   
   of more than one instance updating the various stats files at midnight and   
   racing with each other, e.g. (nodes 11, 6, and 1 are all different instances   
   of sbbs):   
      
   events11:2026-01-07 00:00:01  BBS Events New Day - Prev: Tue Jan 06 2026 12:00   
   am   
   events11:2026-01-06 00:00:14  BBS Events New Day - Prev: Mon Jan 05 2026 12:00   
   am   
   events6.log:2026-01-07 00:00:08  BBS Events New Day - Prev: Tue Jan 06 2026   
   12:00 am   
   events.log:2026-01-06 23:59:59  BBS Events New Day - Prev: Wed Jan 07 2026   
   12:00 am   
      
   The "prev" date being in the future is an obvious check, but also   
   double-checking the date in the dsts.ini files after we open each for update   
   and log if the date is unexpectedly already set to today or the future.   
      
   This issue likely didn't effect anyone but Vertrauen, but I observed it when   
   scrutinizing 'slog' and SBBSCTRL->BBS->View->Statistics Log output and   
   noticed a stuttering in the logged dates, e.g.   
      
   26/01/09 T:  166 L:  20 P:   4 E:  10 F:  22 U: 155M/4     D: 828M/1810   N:2   
   26/01/08 T:  114 L:  16 P:   6 E:  25 F:  12 U:   0M/0     D:   1G/9695   N:1   
   26/01/07 T:   64 L:  17 P:   0 E:  11 F:   4 U:   0M/1     D: 895M/2002   N:1   
   26/01/06 T:    0 L:   0 P:   0 E:   0 F:   0 U:   0M/0     D:   0M/0      N:0   
   26/01/05 T:    0 L:   0 P:   0 E:   0 F:   0 U:   0M/0     D:   0M/0      N:0   
   26/01/06 T:   55 L:   9 P:   2 E:  14 F:   7 U:   0M/0     D:   3G/6981   N:1   
   26/01/05 T:  519 L:  13 P:   4 E:   8 F:   4 U:   0M/0     D: 671M/2241   N:3   
   26/01/04 T:  234 L:  17 P:   7 E:  44 F:   2 U:   0M/0     D: 251M/1209   N:2   
   26/01/03 T:  120 L:  23 P:   5 E:  41 F:   8 U:   0M/0     D: 377M/3061   N:25   
   26/01/02 T:  189 L:  13 P:   5 E:  25 F:   8 U:   0M/0     D: 785M/5561   N:5   
   26/01/01 T:   81 L:  20 P:   6 E:  36 F:  16 U:   1M/1     D: 400M/3258   N:4   
   --- SBBSecho 3.34-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 275 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