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,642 of 49,116   
   Rob Swindell (on Windows 11) to Git commit to main/sbbs/master   
   docs/v321_new.txt src/sbbs3/answer.cpp s   
   11 Jan 26 01:52:31   
   
   TZUTC: -0800   
   MSGID: 54073.syncprog@1:103/705 2dc97c18   
   PID: Synchronet 3.21b-Linux master/177a369d2 Jan 04 2026 GCC 12.2.0   
   TID: SBBSecho 3.34-Linux master/86159f6a2 Jan 10 2026 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/commit/418e4413718b7d5ffde113f7   
   Modified Files:   
   	docs/v321_new.txt src/sbbs3/answer.cpp src/sbbs3/ctrl/MainFormUnit.cpp   
   src/sbbs3/ntsvcs.c sbbs_ini.c sbbs_ini.h sbbscon.c src/sbbs3/scfg/scfg.c   
   scfgsrvr.c src/sbbs3/startup.h   
   Log Message:   
   Built-in detection / short inactivity timeout of dumb terminal (bot) logins   
      
   Configured in SCFG->Servers->Terminal Server->Max Dumb Login Inactivity, the   
   default is one minute (60s). This solution is much more reliable than the   
   login.js method since it's quite possible that the display of the "answer"   
   file can pause (e.g. with a [Hit a key] prompt) before the login module even   
   executes.   
      
   Any auto-terminal-type detection (e.g. ANSI, PETSCII, UTF-8) will defeat this   
   (short) inactivity setting and use the normal login inactivity duration   
   (now called "Max User Login Inactivity").   
      
   The other big change included here is for graceful detection of startup   
   structure version changes (via size checking). When mixing revisions of SBBS   
   libs and apps, it was possible to have an insufficiently allocated startup   
   structure passed around and memory-initialized beyond its bounds or otherwise   
   have some startup structure elements (e.g. settings) read or written at their   
   incorrect offset. I discovered this while adding to the bbs_startup_t but   
   upon review found that there was no size checking for the global_startup_t and   
   the sbbs_read_ini() function returned no success or failure indication.   
   --- 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