Subj : Re: Moving SBBS logging o
To   : DIGITAL MAN
From : Dumas Walker
Date : Sat Feb 17 2024 10:48 am

> It goes to syslog (the daemon/service, not necessarily the file "syslog"). Loo
> at your syslog configuration file to find out which *files* it goes to. Or use
> omething like journalctl (if you have it) to view them based on service. There
>  also tools like lnav which are nice for viewing logs.

I looked into journalctl.  It is supposed to show syslog output with the
option '-u syslog' but it does not.  It claims there are "no entries."  It
does not know what 'sbbs' is, presumably because I don't run it daemonized,
so there are also "no entries."

To my knowledge, there is no syslog configuration file because rsyslog is
not installed -- it was replaced with the stupid systemd journaling crap
which, as I have figured out, doesn't work so good.  I actually just
checked.  /etc/rsyslog.d is still there, but its contents are being ignored
by the broken new replacement.

It is like a linux dev decided to answer a question that no one asked --
how can I make it harder for users who are good with cat, grep, head, tail,
etc., to check their logs? -- and the predictably dumb answer was journalctl.

So I don't want synchronet logging going to "syslog" anymore, file or
otherwise.  Now that I have taken syslog off the command line, where is sbbs
logging to?  It currently looks like nowhere, so I'd like to fix that if
possible.

If not possible, I will check into reinstalling rsyslog and living with
everything (supposedly) being logged twice, which seems like a real PITA.


 * SLMR 2.1a * "For there is no sea, with out the dolphin" -- Oppian

---
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

.