F20 - Unintended consequences of no default MTA - How best to fix

Lars E. Pettersson lars at homer.se
Tue Dec 31 23:40:08 UTC 2013


On 12/31/2013 10:49 PM, Rahul Sundaram wrote:
> No.  That's just blatantly wrong.  journalctl's output is a pixel
> perfect match of /var/log/messages.

No, it's not:

journalctl -f contains the following
Jan 01 00:10:01 tux systemd[1]: Starting Session 98 of user root.
Jan 01 00:10:01 tux systemd[1]: Started Session 98 of user root.
Jan 01 00:10:01 tux CROND[9317]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jan 01 00:20:01 tux systemd[1]: Starting Session 99 of user root.
Jan 01 00:20:01 tux systemd[1]: Started Session 99 of user root.
Jan 01 00:20:01 tux CROND[9557]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jan 01 00:30:01 tux systemd[1]: Starting Session 100 of user root.
Jan 01 00:30:01 tux systemd[1]: Started Session 100 of user root.
Jan 01 00:30:01 tux CROND[9726]: (root) CMD (/usr/lib64/sa/sa1 1 1)

tail /var/log/messages

Jan  1 00:10:01 localhost systemd: Starting Session 98 of user root.
Jan  1 00:10:01 localhost systemd: Started Session 98 of user root.
Jan  1 00:20:01 localhost systemd: Starting Session 99 of user root.
Jan  1 00:20:01 localhost systemd: Started Session 99 of user root.
Jan  1 00:30:01 localhost systemd: Starting Session 100 of user root.
Jan  1 00:30:01 localhost systemd: Started Session 100 of user root.

tail /var/log/cron

Jan  1 00:10:01 localhost CROND[9317]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jan  1 00:20:01 localhost CROND[9557]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jan  1 00:30:01 localhost CROND[9726]: (root) CMD (/usr/lib64/sa/sa1 1 1)

Spot the differences?

Lars
-- 
Lars E. Pettersson <lars at homer.se>
http://www.sm6rpz.se/


More information about the users mailing list