Carlos E. R. wrote:
On 2014-06-03 22:29, Felix Miata wrote:
On 2014-06-03 03:08 (GMT-0400) Dirk Gently composed:
1. systemd doesn't produce ASCII (or for that matter, UTF) log files, it produces binary blob log files.
:~(
Which means you can't just browse through a log file using grep, awk, and/or more (or less).
Or F3 in an OFM, or in such GUI apps as file manager, text editor or web browser.
2. systemd eliminates separate log files... so if you're looking for ntp messages, we no longer have ntp log files... now we have to wade through the whole combined (binary only) logfile
:~(
3. The old time tested method of keeping log files small and maneagble (daily rotation) is now also broken, YATFUBSD...
:~(
But all those are simply false!
I am using systemd, as everybody with openSUSE, and I have plain text logs, which I do browse with grep and the rest. I get separate log files, and I choose how they are distributed. And they are rotated and compressed properly, as always.
Systemd does generate a binary log of its own, which can be persistent, on disk, or just for the current boot. But nothing impedes you to use a syslog daemon as always.
There have been discussions about which should be the default setting in openSUSE, but so far, I think that syslog is staying by default, and if not, you can easily activate it.
The systemd persistent binary log has horrible search performance, unless you don't use magnetic media for storage. The devs did not see a problem with it, because they were using fast flash devices, on which seek operations are instantaneous, there is no head movement.
Which is a pity, because if it worked correctly, being a database, it is easier to select events for display. But not when it takes several hours to get at them (no kidding).
Another example of just how poorly thought out this whole thing is. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org