On 02/26/14 19:23, lee wrote:
What is the purpose of this log duplication? When systemd has its
own
logs, it doesn´t seem necessary to duplicate them by sending their
contents to syslogd.
One could also ask why systemd duplicates the logging formerly only done
by syslogd.
For me looking through my ASCII-based text-logs created by syslogd is
far faster than using journalctl. Things that takes over 25 minutes with
journalctl, only takes 66 seconds grepping the syslogd logs. (see bug
1047719, that no-one seems to care about)
ASCII-based logs can be read by anybody using any editor. To read the
journal you need journalctl, or similar program, as the journal is
binary and not readily readable.
Another reason is that there still exist programs/daemons/etc. that rely
on the logs in /var/log.
If you do not like syslogd, well F20 does not ship it anymore...
Lars
--
Lars E. Pettersson <lars(a)homer.se>
http://www.sm6rpz.se/