Hello, On 09/27/2012 09:54 AM, Guido Berhoerster wrote:
* Peter Czanik <pczanik@fang.fa.gau.hu> [2012-09-27 09:06]:
The primary advantage of the journal is, that it's heavily integrated with the init system (systemd): - logging of early boot related messages is possible, while (r)syslog(-ng) can't be started early enough and only with ugly hacks to catch part of those. - much better logging of apps started by systemd As you said, early boot logging can be made to work without completely reinventing the wheel. Part of it. Just checked again, the journald logs cover logs from a much earlier phase of the boot process...
This may no be possible with syslog-ng, however rsyslogd which is the openSUSE default syslog has supported securely recording of pid, gid, uid for a long time, more recently it has become capable of recording the path of the executable, command name and full commandline obtained via /proc. The last time I checked it, it was still experimental code...
It has also a circular log file, so it never fills the HDD, but uses a given percentage of it (5% by default AFAIR). So log rotation is not any more a problem. rsyslogd has fixed-length log rotation built in which can achieve exactly the same. And labeled as "to be removed soon" in the documentation...
And the major advantage from the syslog(-ng) point of view, that most of it can be disabled while the useful part continues to work. As it will still follow apps started by systemd, collect status messages, etc. which is not possible by any syslog implementation on that level. As stated above, implementing this doesn't require to replace the whole logging infrastructure. Not the whole, just part of it, so early boot, which was always a major pain, is covered correctly. And one can stick to syslog on machines where filtering, scripting, central logging is necessary. But it's just a small portion of openSUSE users. Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org