Отправлено с iPhone
6 сент. 2016 г., в 22:42, Michael Fischer
написал(а): 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.
Not really. It depends on how syslog-ng gets messages from journald. If it is configured as journald client (as opposed to listening on socket) then it can only get messages that had been stored. Please read https://www.freedesktop.org/software/systemd/man/journald.conf.html for details.-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org