On Mon, 08 Feb 2021 20:20:46 +0900, Olaf wrote in message <87sg66vm9d.fsf@quark>:
> Hi Steve, > > # I'm not a systemd fan. I just happen to run two Debian servers at > the # office and gained some experience with systemd ... most of it > the hard # and less than pleasant way :-/ ..<snip>. > The issue is with systemd's log configuration, the gory details of > which you can explore by going down the rabbit hole that starts at > > https://manpages.debian.org/buster/systemd/journald.conf.5.en.html > > If you don't want the systemd-journald.service to log anything, just > say > > Storage=none ..canary-bird-in-coal-mine idea: If you do _both_ ways described in "Journal events can be transferred to a different logging daemon in two different ways." in the "FORWARDING TO TRADITIONAL SYSLOG DAEMONS" section of https://manpages.debian.org/buster/systemd/journald.conf.5.en.html , and diff those 2 log streams, you should be able to catch any new rabbit hole shenanigans. Etc. Not tested here. > in journald.conf and be done with it. Log messages are still > forwarded to a syslog socket so if you have rsyslog installed you > should be good. > > Of course, switching to Devuan may be an easier long term solution :-) > Or some other distro that let's you choose your prefered init system. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
