Subj : sbbsecho issue
To   : DIGITAL MAN
From : Dumas Walker
Date : Wed Sep 10 2025 08:59:20

>  > Node (618:250/1.9) externally locked via:
>  > /sbbs/fido/out.26a/00fa0001.pnt/00000009.bsy (since ??:??)

> 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 numbe
> 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.

It is set to "Warning".  Is that more or less severe than "Informational"?

The attempts were set at 60 so I lowered it.  What happens when it "gives
up"?

Regardless they were *not* written to the console.  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.


 * SLMR 2.1a * Mind like a steel trap - rusted shut!
---
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.