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.

   SYNCHRONET      Rob Swindell fetishistic worship forum      43,341 messages   

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

   Message 42,345 of 43,341   
   Dumas Walker to DIGITAL MAN   
   sbbsecho issue   
   11 Sep 25 11:31:23   
   
   TZUTC: -0500   
   MSGID: 73958.sync@723:320/1 2d295041   
   REPLY: 54850.sync@1:103/705 2d27d98d   
   PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0   
   TID: SBBSecho 3.29-Linux master/7acaccaf1 Sep 08 2025 GCC 12.2.0   
   BBSID: CAPCITY2   
   CHRS: CP437 2   
   FORMAT: flowed   
   >  > It is set to "Warning".  Is that more or less severe than "Informational"?   
      
   > A warning is more severe than informational and that means that Info-level   
   > messages would *not* be written to the sbbsecho.log. I recommend you change   
   > that back to the default (info) or if/when you're having issues, you change   
   it   
   > to Debug.   
      
   I don't suspect that I changed it as I would have had no reason to and was   
   not even aware of that setting until this conversation.  I suspect it has been   
   set that way, by default, since I first installed synchronet ~20 years ago.   
      
   I will set it to the more recent default.   
      
   >  > They were written in   
   >  > the terminal window when sbbsecho was run manually but, in normal   
   >  > operation, they do *not* show up on the sbbs console or in syslog.   
      
   > Correct, because you changed the log level from info to warning which   
   > instructed SBBSecho to only log warnings and errors to the sbbsecho.log file.   
      
   So it will show up in the sbbs console, and the syslog, if set to   
   "informational"?   
      
   > SBBSecho is behaving exactly as designed and documented, it appears to me.   
      
   That might be but if sbbsecho is getting a "lock" on a non-existant file   
   (which it should be able to tell because it cannot find the proper time to   
   display - it displays ??:??), I would strongly suggest the message in that   
   case is more than just "informational"...  there *is* something wrong that   
   *will* require intervention if you want mail to keep flowing.   
      
      
    * SLMR 2.1a * This just in: Research causes cancer in rats!   
   ---   
    þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 610 700 840 860 880   
   SEEN-BY: 226/30 227/114 229/110 206 317 400 426 428 470 700 705 266/512   
   SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58   
   SEEN-BY: 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426   
      

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


(c) 1994,  bbs@darkrealms.ca