Subj : Re: Moving SBBS logging o To : GAMGEE From : Dumas Walker Date : Sun Feb 18 2024 10:35:00 > Yes, Slackware does not, and likely never will, use systemd. That's a > Good Thing in my opinion. :-) Indeed. I run devuan on a couple of boxes for that reason, but I have found it is not real reliable for my use if I need X windows. So it runs on cli only machines and in a couple of VMs. > 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. It might except... > 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. It is not so much that, but journalctl is supposed to be able to show me the syslog logging if I give it a '-u syslog' but it reports there are no entries. Oooops! ;) * SLMR 2.1a * bort etry hoot the SOB! --- þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) .