-=> Dumas Walker wrote to DAN CLOUGH <=-

 >  DW> Several years ago I set my BBS up to write the log to syslog.
 >  DW> Recently, some shit for brains decided that having syslog was
 >  DW> "bad" so now there is no easy way to just load syslog and search
 >  DW> it.

 >  DW> I want to revert back to having Synchronet keeps its own log.
 >  DW> How do I do that?

 > I am using Slackware Linux, and in my /etc/syslog.conf I've added this
 > near the bottom of the file:

 DW> Sounds like maybe Slackware Linux, or at least the version you
 DW> are running, has not switched over to systemd?  That happened a
 DW> few debian versions ago.

Yes, Slackware does not, and likely never will, use systemd.  That's a 
Good Thing in my opinion.  :-)

 DW>  With the latest version, they've replaced rsyslog with some
 DW> systemd journaling.  I can learn some new tool(s) to get to the
 DW> syslog output I want, *IF* they worked as documented which they
 DW> do not here.

Yep, I have a Debian box and some other variants and have noticed that 
too.  I don't know much about it, but the "journalctl" command may help.

 > # Synchronet BBS logging - added by Dan C. 2/17/19
 > local3.*                        -/var/log/sbbs.log

 > The "3" on the end of the "local" keyword is because I've also changed
 > my /sbbs/ctrl/sbbs.ini to have this in the [UNIX] section at the bottom:

 > ; Defaults to using the USER facility.
 >     LogFacility = 3

 > The result of these two settings produces my log in /var/log/sbbs.log

 > Hope that helps!

 DW> I may have to reinstall rsyslog and live with the syslog output
 DW> being both written to file and (maybe) journaled (although it
 DW> does not really appear to be like it is supposed to be).

That's probably an option; don't think it would hurt anything to have two 
logs, if it allows you to use the tools you prefer.  Good luck.


... All the easy problems have been solved.
--- MultiMail/Linux v0.52
 þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL