TZUTC: -0500
MSGID: 73938.sync@723:320/1 2d26a431
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
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.

Thanks!


 * SLMR 2.1a * Photons have mass? I didn't know they were Catholic...
---
 þ 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