Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Sunday December 21 2014, @04:54PM   Printer-friendly
from the show-stopper-or-rare-event? dept.

Noted Linux expert Chris Siebenmann has described two catastrophic failures involving systemd.

One of the problems he encountered with systemd became apparent during a disastrous upgrade of a system from Fedora 20 to Fedora 21. It involved PID 1 segfaulting during the upgrade process. He isn't the only victim to suffer from this type of bad experience, either. The bug report for this problem is still showing a status of NEW, nearly a month after it was opened.

The second problem with systemd that he describes involves the journalctl utility. It displays log messages with long lines in a way that requires sideways scrolling, as well as displaying all messages since the beginning of time, in forward chronological order. Both of these behaviors contribute to making the tool much less usable, especially in critical situations where time and efficiency are of the essence.

Problems like these raise some serious questions about systemd, and its suitability for use by major Linux distros like Fedora and Debian. How can systemd be used if it can segfault in such a way, or if the tools that are provided to assist with the recovery exhibit such counter-intuitive, if not outright useless, behavior?

Editor's Comment: I am not a supporter of systemd, but if there are only 2 such reported occurrences of this fault, as noted in one of the links, then perhaps it is not a widespread fault but actually a very rare one. This would certainly explain - although not justify - why there has been so little apparent interest being shown by the maintainers. Nevertheless, the fault should still be fixed.

 
This discussion has been archived. No new comments can be posted.
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 VLM on Sunday December 21 2014, @06:30PM

    by VLM (445) Subscriber Badge on Sunday December 21 2014, @06:30PM (#128071)

    the manual configuration of just about everything.

    Doing it by hand = doing it wrong. If not puppet or chef, something homegrown. Computers are supposed to eliminate manual labor, not move it to keyboard/mouse.

    Less than 10 minutes from cold dead iron to working and that includes the freebsd install. Images are of course much faster and seem limited solely by NAS bandwidth (which means pretty fast, except when it isn't...) I guess there's ways to automate OS installers but I'm not doing that enough to be motivated to set it up. I would guess slackware can't be much worse than freebsd.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2, Informative) by Anonymous Coward on Sunday December 21 2014, @06:32PM

    by Anonymous Coward on Sunday December 21 2014, @06:32PM (#128073)

    Why would I want to waste my time with Puppet or Chef when I'm just installing Linux on a single workstation for my own personal use?

    I just use Ubuntu, which sets up everything I need for me, so I don't have to do it myself. Slackware does none of this.

    • (Score: 2) by VLM on Sunday December 21 2014, @06:45PM

      by VLM (445) Subscriber Badge on Sunday December 21 2014, @06:45PM (#128077)

      on a single workstation

      Thats a world far away from me... I suppose when you reinstall due to hardware failure or whatever, its nice to be automated and do it in minutes/seconds instead of hours of rework.

      Then again you probably have a lot less work to do... No need to screw around with single signon and kerberos and all that