On Tue, Sep 06, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Content-ID:
El 2016-09-06 a las 14:12 -0400, Michael Fischer escribió:
On Sat, Sep 03, Carlos E. R. wrote:
Next step is stopping systemd keeping the journal. There are settings for this which I'll have to find out again.
Arrggghhh.
syslog-ng may "conflict" with systemd-journald, but that seems..odd.
Insofar as I've just discovered syslog-ng rather depends on a running systemd-journald in order to get any messages. I had enabled & started syslog-ng, and disabled & stopped systemd-journal. Today I notice that I have nothing except stats() in /var/log/messages. Everything else stopped at the same point where I turned off systemd-journald...
Oh :-((
So it seems not so much either/or as "would you like us to scribble the messages in the old-fashioned way to /var/log AS WELL?"
If someone from SuSE knows definitively if this is How It Works, clarification would be welcome.
Have you tried to leave systemd-journal running, but with the
Storage=none
setting? (in /etc/systemd/journald.conf)
Hmm. No, but that's a thought. $ du -sh /var/log/journal 41M /var/log/journal/69c54807c3cb473b82a49c7b7e022c37 Is not all that bad, actually. But.... Ok, just tried it, making sure that ForwardToSyslog=yes Storage=none And after the ritual `systemctl daemon-reload; systemctl restart systemd-journald.service` .... `logger -p LOCAL4.INFO "test message"` goes nowhere. So I'm either misunderstanding journald.conf(5), or the line in there which says """ "none" turns off all storage, all log data received will be dropped. Forwarding to other targets, such as the console, the kernel log buffer or a syslog daemon will still work however. """ is lying. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org