Weekly edition	Kernel	Security	Distributions	Contact Us	Search
Archives	Calendar	Subscribe	Write for LWN	LWN.net FAQ	Sponsors

LCE: Systemd two years on

Posted Nov 8, 2012 10:00 UTC (Thu) by BradReed (subscriber, #5917)
In reply to: LCE: Systemd two years on by kenmoffat
Parent article: LCE: Systemd two years on

I am also unsure with what the major problem is with system logs being in plain text. A failure in being able to read the last 10 messages of a particular service? I guess grep and tail are too old fashioned for modern linux users.

(Log in to post comments)

Posted Nov 8, 2012 11:15 UTC (Thu) by dan_a (subscriber, #5325) [Link]

Grep and tail are fine for users (or for advanced users.) They are less fine for automated log parsing.

I'm a bit worried, though, about how divergent the platforms for server and desktop Linux might end up becoming by going down the path of Journal vs. Syslog - server admins don't always have the same needs as desktop users, but it can't be helpful if the tools they use diverge too much.

LCE: Systemd two years on

Posted Nov 8, 2012 14:38 UTC (Thu) by cmorgan (guest, #71980) [Link]

Nothing prevents journald from maintaining backwards compatibility:

From http://www.freedesktop.org/software/systemd/man/systemd-j...

"
Kernel Command Line

A few configuration parameters from journald.conf may be overridden on the kernel command line:

systemd.journald.forward_to_syslog=, systemd.journald.forward_to_kmsg=, systemd.journald.forward_to_console=
Enables/disables forwarding of collected log messages to syslog, the kernel log buffer or the system console.
"