Re:Ian Jackson Resigns from Debian Technical Committee
by jude- on Wednesday November 19, 2014 @04:04PM
(#8632613)
Either I'm using journald to log to a binary format, or I'm having journald forward everything to syslog. If I'm trying to avoid binary logs in the first place, then there's really no point for journald to be running--just forward directly to syslog in the first place. Journald is just dead weight in this use-case.
Re:Ian Jackson Resigns from Debian Technical Committee
by teddyh on Thursday November 20, 2014 @04:27AM
(#8634968)
Actually, journald exists for a number of reasons, listed here:
https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBA...
As far as I can tell, the whole brouhaha started when there was a bug in the packaging of syslog-ng so it would not start properly after installing systemd. Since syslog-ng was not running, the only logs left were journald’s binary logs, and people assumed that “systemd ate my log files!”. No. It was a bug, the bug was not even in systemd, your log files will always be where you want them.
Unless you uninstall your syslog daemon, but then you are on your own.