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,328 of 43,341    |
|    Digital Man to Dumas Walker    |
|    sbbsecho issue    |
|    09 Sep 25 16:54:15    |
      TZUTC: -0700       MSGID: 54844.sync@1:103/705 2d26ca63       REPLY: 73938.sync@723:320/1 2d26a431       PID: Synchronet 3.21a-Linux master/7acaccaf1 Sep 08 2025 GCC 12.2.0       TID: SBBSecho 3.29-Linux master/7acaccaf1 Sep 08 2025 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       FORMAT: flowed       NOTE: FSEditor.js v1.105        Re: sbbsecho issue        By: Dumas Walker to DIGITAL MAN on Tue Sep 09 2025 10:53 am               > I ran into a problem with sbbsecho this morning. I noticed the FIDOIN &        > FIDOOUT events were hanging. I checked the sbbsecho.log and could not find        > any error messages, and there were no error messages showing up in the        > console.        >        > Killing the hung instances, opening a terminal, and running sbbsecho by hand        > gave me this information:        >        > Node (618:250/1.9) externally locked via:        > /sbbs/fido/out.26a/00fa0001.pnt/00000009.bsy (since ??:??)        >        > I checked and that bsy file did not exist. However, I also noticed that        > there was a directory permission issue. Once fixed, sbbsecho continued and        > exited normally.        >        > Would it be possible to have some error message show up either on the sbbs        > console, or at least the sbbsecho.log, when something like this is        > happening? As noted above, the only way I saw and fixed the error was by        > running        > sbbsecho manually.              That same message would have been written to the sbbsecho.log file. The lock       attempt is retried (after the configurable number of BSO lock delay seconds)       and gives up (and logs a warning about "Giving up") after the configured       number of BSO lock attempts. All of these messages would be written to your       sbbsecho.log file as well as the console. The only reason they would not be       written to the log file is if you had your "Log Level" set to something less       (more severe) than "Informational" in echocfg->Global Settings.       --         digital man (rob)              Steven Wright quote #23:       My mechanic told me, I couldn't repair your brakes, so I made your horn louder       Norco, CA WX: 81.0øF, 48.0% humidity, 10 mph WNW wind, 0.00 inches rain/24hrs       --- SBBSecho 3.29-Linux        * 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