On Fri, Sep 02, Anton Aylward wrote:
On 09/02/2016 09:05 AM, Carlos E. R. wrote:
For some reason, rsyslog was the default on openSUSE some years back, that's the reason I have it. And it's given me problems.
If rsyslog gave you problems, what makes you think the more complex, more advanced syslog-ng wont?
Speaking personally, the config syntax for -ng is *far* nicer to work with, irrespective of whether I'm shooting for something "complex" or simple. Oh, Carlos, as I just went through this exercise this morning... be prepared for huge amounts of systemd spam in /var/log/messages. See http://www.linuxquestions.org/questions/fedora-35/systemd-log-flood-session-... as just one example I found out there. Lots of bad "just filter it" answers out there, on that and other threads, but page two of the above seems to have figured out the appropriate workaround: `sudo loginctl enable-linger root`. Quoting the hypothesis from the above, and trying it now: "Systemd is running a per-user systemd for root whenever a session is started, e.g. to run a cron job. Then when root’s last session is closed, the per-user systemd is killed. The spew of log messages has to do with the the spawning and killing of that per-user systemd." Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org