Stories
Slash Boxes
Comments

SoylentNews is people

The Strained Relationship Between Systemd and Syslog

posted by martyb on Sunday April 19 2015, @06:02PM   Printer-friendly
from the with-all-this-logging-we-need-a-lumberjack dept.

An Anonymous Coward writes:

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.

 
This discussion has been archived. No new comments can be posted.
The Strained Relationship Between Systemd and Syslog | Log In/Create an Account | Top | 36 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by danomac on Monday April 20 2015, @05:10PM

    by danomac (979) on Monday April 20 2015, @05:10PM (#173193)

    For the record, I've never had systemd or journald cause me any grief yet.

    I have, but I only discovered it recently as I rarely reboot my computer.

    I use an Intel fakeraid (via mdadm) due to my dual-boot with Windows. For some reason, `systemctl reboot` and `systemctl shutdown` hang, and on restart cause the IMSM raid to break and rebuild, and there's no indication as to why. During my testing, `systemctl poweroff` works normally.

    I haven't had time to even figure out how to compare the three targets to see if there's any difference between them, nevermind coming up with some sort of solution.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 2) by frojack on Monday April 20 2015, @10:05PM

    by frojack (1554) on Monday April 20 2015, @10:05PM (#173301) Journal

    It seems that all three of those commands go to the same place [freedesktop.org] and systemd replaces itself with /usr/lib/systemd/systemd-shutdown with an argument. I suspect the problem is with that shutdown tool.

    Come to think of it, I've had BTRFS barf up its lunch twice, and moved away from it.
    I don't know what caused this, it was running on a systemd machine, so I guess I can't totally rule it out I suppose.

    But it wasn't obviously systemd as far as I can tell.
    Twice in 6 months was too much for me.

    I tend to suspend my machine rather than shutting down, and this all seems to work, but even shutting down has not caused any problems since I moved away from BTRFS. I might revisit BTRFS in a couple releases.

    I've yet see no advantage to systemd.

    --
    No, you are mistaken. I've always had this sig.

    • (Score: 2) by danomac on Monday April 20 2015, @10:40PM

      by danomac (979) on Monday April 20 2015, @10:40PM (#173309)
      Well, I think I'll change kdm's reboot & shutdown commands to `systemctl poweroff` for now.

      I also noticed that shutdowns take a lot longer - about 3 minutes compared to openrc's 20 seconds. systemd seems to get hung up shutting down apcupsd (even though apcupsd indicates it shut down successfully in journalctl) systemd doesn't seem to notice.

      When I was using openrc the IMSM raid array would corrupt at every reboot.

      My laptop has no issues with systemd. Just my main desktop.