-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2016-09-06 a las 15:42 -0400, Michael Fischer escribió:
On Tue, Sep 06, Carlos E. R. wrote:
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.
No, I don't think so. It depends how syslog-ng takes the messages. If it does something similar to read the log file (and I think it does) it will see nothing. I think it reads the files because I started syslog-ng hours after booting, and still got boot messages. This is a pity... I don't like it. I may stay with rsyslog instead. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlfPL9oACgkQja8UbcUWM1xkHgD/fYz9jpaYGOQzW5/n1gGSMtuH JMGwknerF6zY5wLQM8kA/iNC9ZRsHDOJNmjjm1y4tYcejRCFtqObw9J9MlqFu1o2 =NDhR -----END PGP SIGNATURE-----