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,457 of 49,116   
   Rob Swindell (on Windows 11) to Git commit to main/sbbs/master   
   src/sbbs3/jsexec.cpp load_cfg.c   
   01 Jan 26 18:04:26   
   
   TZUTC: -0800   
   MSGID: 53885.syncprog@1:103/705 2dbd3027   
   PID: Synchronet 3.21a-Linux master/48922a15c Dec 17 2025 GCC 12.2.0   
   TID: SBBSecho 3.34-Linux master/8bb133aa7 Dec 30 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/commit/115af6c10653ba0ff98345b4   
   Modified Files:   
   	src/sbbs3/jsexec.cpp load_cfg.c   
   Log Message:   
   Require a successful config load by jsexec, by default (-U to disable)   
      
   The old -R (to force the required config load) is still supported just for   
   backward compatibility, but effectively does nothing.   
      
   The new -U option is really just used for the one special upgrade scenario:   
   going from v3.19 or earlier to v3.20 or later.   
      
   So now... when upgrading from Synchronet v3.19 or earlier to v3.20 or later,   
   sysops will need to run 'jsexec -U update.js'. All other uses of jsexec   
   (including updates between all other versions) should not need the -U option.   
      
   If you're already running v3.20 or later: you don't need to change anything.   
      
   load_cfg() now does the all the prep (e.g. of dirs/paths) even when config   
   files fail to load in this case.   
      
   This fixes the segfault seen when running jsexec with a mismatched [lib]sbbs   
   [.so|.dll]. If load_cfg() fails, don't continue on.   
      
   Also, if a successful config load is not required (the -U option was used),   
   don't print any load_cfg() warnings either (just noise in that case).   
      
   Also fix the exception in jsexec-win32 when calling lprintf() to print the   
   load_cfg warning (if any) before the output_mutex was initialized.   
   --- SBBSecho 3.34-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715   
   SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110   
   SEEN-BY: 229/134 206 275 317 400 426 428 470 700 705 240/1120 5832   
   SEEN-BY: 263/1 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca