Subj : sbbsecho issue
To   : DIGITAL MAN
From : Dumas Walker
Date : Thu Sep 11 2025 11:31 am

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

You are viewing proxied material from bbs.kd3.us. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.