SoylentNews is people
SoylentNews
from the with-all-this-logging-we-need-a-lumberjack dept.
World-renowned Unix master Chris Siebenmann has written an article entitled 'I wish systemd would get over its thing about syslog'. It addresses the strained relationship between the systemd init system and the traditional syslog approach to logging used on many Linux systems.
Chris writes:
Anyone who works with systemd soon comes to realize that systemd just doesn't like syslog very much. In fact systemd is so unhappy with syslog that it invented its own logging mechanism (in the form of journald). This is not news. What people who don't have to look deeply into the situation often don't realize is that systemd's dislike is sufficiently deep that systemd just doesn't interact very well with syslog.
This is a must-read article for anyone who needs to use systemd and syslog together.
(Score: 2, Redundant) by frojack on Sunday April 19 2015, @07:32PM
Agreed. Logging is almost universally abused.
Logging (regardless of platforms) tend contain massive amounts of stuff that doesn't need to be logged at all, is obtuse, and only meaningful to the coder, using terminology that makes them deliberately unintelligible.
And any complaining users are instructed to change their system logging level to avoid these messages. Never considering that you may need logging at a specific level for other equally non-compliant software.
No, you are mistaken. I've always had this sig.