On Wed, Dec 21, 2016 at 10:22 AM, Per Jessen
In this machine I disabled completely the journal: This works with rsyslog, but not with syslog-ng, I believe.
I expect it would work with both, I'm sure they use the same interface.
Hmm, I have just changed to storage=none on a test system, and syslog-ng does indeed not work. Interesting, I wonder why that is.
Default configuration of syslog-ng is using system() source and system() source on Linux adds systemd-journal() source if it detect that it runs under systemd. systemd-journal() source actively pulls log entries from journal files. "storage=none" means no journal files - no log entries for syslog-ng source as well. Actually I'm rather puzzled why rsyslog works for you at all :) On test TW installation I do not see any journal-specific part in rsyslog configuration and ForwardToSyslog apparently defaults to "no" so rsyslog should not receive data even via socket ... indeed, after installing and starting rsyslog I do not get any test message via it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org