Carlos E. R. wrote:
El 2016-09-07 a las 09:42 +0200, Per Jessen escribió:
ianseeks wrote:
There used to be a config option in systemd to forward all logs to syslog/ rsyslog. You can try find that setting but they were going to deprecate the option because rsyslog/syslog extract the data from the jounral themselves now.
Yep - that option is either gone, on by default or as you say, not needed. When you install either log-daemon, it just works.
But the way it "just works" by default is by reading the log files, which means that there is a delay.
I meant it just works as in "you don't need to do anything extra, it just works". Anyway, which log files Carlos? Neither syslog daemon reads any logfiles. (does systemd even write any files meant for interfacing with?) As for a delay - even if there is measurable delay, who cares? It's a log file, not an interactive tracing or debugging facility.
First systemd processes the entries, writes them to file, them syslog gets them, processes them, and writes them. Not simultaneously.
I think I am missing your point. AFAIK, by default, syslog-ng and rsyslog both communicate directly with systemd-journald. Alternatively, they can use the socket provided by systemd. (/run/systemd/journal/syslog).
If systemd has problems, syslog will also have them.
If systemd has problems, you've got bigger problems to worry about. :-) I don't know where this thread is going - both rsyslog and syslog-ng are well-functioning syslog daemons. I personally favour syslog-ng as I find it much easier to work with. -- Per Jessen, Zürich (19.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org