Announcement

Collapse
No announcement yet.

Systemd 227 To Gain Crash Automatic Reboot Option, New Network Features

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Systemd 227 To Gain Crash Automatic Reboot Option, New Network Features

    Phoronix: Systemd 227 To Gain Crash Automatic Reboot Option, New Network Features

    Systemd 227 hasn't been released yet but it appears that it will be coming out quite soon. Here's a look at some of the changes...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    And can it save the crashlog?

    Comment


    • #3
      Originally posted by bitman View Post
      And can it save the crashlog?
      Isnt the crashlog part of the coredump that the kernel automatically saves?
      All opinions are my own not those of my employer if you know who they are.

      Comment


      • #4
        Why stop there, just make systemDos and get it overwith so we can go back to the regular linux we wanted in the first place.

        Comment


        • #5
          Originally posted by _ck_ View Post
          Why stop there, just make systemDos and get it overwith so we can go back to the regular linux we wanted in the first place.
          Feel free to develop Linux as you see fit. Let others do the same. It is that simple.

          Comment


          • #6
            When what crashes? Systemd? Thats stupid. Is it so bloated that it hangs the machine and drags it into a reboot? No wonder people hate systemd.
            Kernel? Already reboots if configured so? If kernel takes an undetected hang? Not a chance, systemd won't detect it.
            This "feature" looks like a brainfart to me.

            How about hooking systemd to a soft watchdog in the kernel which then uses real watchdogs if available.
            Soft registry of identification id's in the watchdog with timeout deadlines to reboot.
            If a process misses deadline the kernel reboots. If the kernel hangs, the deadlines are missed in hardware and then hardware watchdog reboots.
            This way one can do soft realtime detection of hangs of all sorts.

            Comment


            • #7
              @milkylainen
              Sorry. But everything that has "timeout" or "deadline" in it sounds like a bloody horrible idea for this use-case. There should be a saner way to do this.

              Originally posted by _ck_ View Post
              Why stop there, just make systemDos and get it overwith so we can go back to the regular linux we wanted in the first place.

              They're takin' our (terribly messy and badly written) shell scripts! Our shell scripts!!

              Last edited by unixfan2001; 01 October 2015, 02:41 PM.

              Comment


              • #8
                Originally posted by MoonMoon View Post

                Feel free to develop Linux as you see fit. Let others do the same. It is that simple.
                Slight correction. Feel free to start a new project OS as you see fit. Let the primary drivers of most current Linux development do the same.

                Comment


                • #9
                  Originally posted by unixfan2001 View Post
                  They're takin' our (terribly messy and badly written) shell scripts! Our shell scripts!!
                  Have you seen modern OpenRC scripts or only debian's legacy SysV init scripts? They are much more readable, elegant and flexible than most systemd unit files. Starting services is just not something a descriptive language does well, as even the systemd devs realize by now. That is the reason why several services need a lot of unique binary code inside systemd to function. In those situations a shell script would have been a lot more elegant.

                  Comment


                  • #10
                    " That is the reason why several services need a lot of unique binary code inside systemd to function. In those situations a shell script would have been a lot more elegant." can you elaborate on that with some comparative examples?

                    Comment

                    Working...
                    X