systemd 257-rc2 Released With New systemd-keyutil Tool

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • onlyLinuxLuvUBack
    Senior Member
    • May 2019
    • 669

    #11
    Please someone rewrite it with ai bot in rust

    Comment

    • Kjell
      Senior Member
      • Apr 2019
      • 689

      #12
      Originally posted by Britoid View Post
      If you read the article, you would notice that it's not introducing any functionality but moving functionality out of existing systemd utils into their own CLI utility.
      Did you read the article?

      "Systemd 257-rc1 introduced expanded Varlink support, MPTCP as a supported socket protocol for socket units, systemd-boot menu support for volume up/down rocker handling, a new systemd-sbsign tool for signing EFI PE binaries, and many other new additions and other changes. [...] there is one new tool included in the form of systemd-keyutil."

      TLDR: systemd-257 added more bloat


      Originally posted by Britoid View Post
      Thought people liked the purist "DO ONE THING AND DO IT WELL" thing?
      Systemd can't even do one thing properly like shut down the system

      A stop job is running for Session c1 of user work (2min 17s / 3min 30s)
      Last edited by Kjell; 17 November 2024, 05:40 AM.

      Comment

      • NekkoDroid
        Junior Member
        • Feb 2024
        • 43

        #13
        Originally posted by Kjell View Post
        Systemd can't even do one thing properly like shut down the system

        A stop job is running for Session c1 of user work (2min 17s / 3min 30s)
        Sorry one of your processes doesn't actually listen to quit signals or is taking ages to actually stop, but that is hardly systemd's fault. Also upping the default timeout for systemd force stopping the process from 90s to 210s is also on you.

        Comment

        • Kjell
          Senior Member
          • Apr 2019
          • 689

          #14
          Originally posted by NekkoDroid View Post

          Sorry one of your processes doesn't actually listen to quit signals or is taking ages to actually stop, but that is hardly systemd's fault.
          This is just one of very many problems with systemd

          I've never seen this particular problem in years with reliable inits like s6 or Dinit

          Originally posted by NekkoDroid View Post
          Also upping the default timeout for systemd force stopping the process from 90s to 210s is also on you.


          This is default systemd settings

          It's literally increasing the timeout limit from 1m 30s by itself while it's counting down

          Comment

          • fong38
            Senior Member
            • May 2022
            • 146

            #15
            Originally posted by Kjell View Post

            I've never seen this particular problem in years with reliable inits like s6 or Dinit
            Because they just SIGKILL the process within a short timespan I presume?

            Comment

            • intelfx
              Senior Member
              • Jun 2018
              • 1139

              #16
              Originally posted by Kjell View Post
              I've never seen this particular problem in years with reliable inits like s6 or Dinit
              Yeah, because they don't track processes in user sessions
              Kids, take notes: "reliable init" is one whose error handling strategy is to ignore the errors.

              Originally posted by Kjell View Post
              This is just one of very many problems with systemd​
              I'm going to assume the rest of "very many problems" are of the same nature as above.

              Comment

              • Kjell
                Senior Member
                • Apr 2019
                • 689

                #17
                Originally posted by fong38 View Post
                Because they just SIGKILL the process within a short timespan I presume?
                On the contrary, you've just described systemd. It's hurting itself in its confusion

                Originally posted by intelfx View Post
                Yeah, because they don't track processes in user sessions .
                Dinit supports user-mode services, as well as s6

                Originally posted by intelfx View Post
                I'm going to assume the rest of "very many problems" are of the same nature as above


                No, it's a lot worse and these issues are merely a byproduct of complexity introduced by scope-creep.

                Comment

                • intelfx
                  Senior Member
                  • Jun 2018
                  • 1139

                  #18
                  Originally posted by Kjell View Post
                  Dinit supports user-mode services, as well as s6
                  Cool, it supports that theoretically. Now run the exact same configuration, with exact same processes under exact same kind of supervision, under dinit or s6, then we'll talk.

                  Originally posted by Kjell View Post
                  No, it's a lot worse and these issues are merely a byproduct of complexity introduced by scope-creep.
                  So far it's just your words. And given your blatant wishful thinking above, I'm not sensing much weight behind those words.
                  Last edited by intelfx; 17 November 2024, 11:52 AM.

                  Comment

                  • Kjell
                    Senior Member
                    • Apr 2019
                    • 689

                    #19
                    Originally posted by intelfx View Post
                    So far it's just your words. And given your blatant wishful thinking above, I'm not sensing much weight behind those words.
                    Sure? Most people tend to get discouraged when everything isn't pre-configured and handed to them on a silver platter.

                    Comment

                    • mobadboy
                      Senior Member
                      • Jul 2024
                      • 173

                      #20
                      systemd continuing to revolutionize Linux in the best way possible. Linux userland was so unbelievably shit in the sysvinit days, and rc.d/upstart/openrc are only slightly less terrible. I can never understand why alpine continues to pander to the haters.

                      Originally posted by Kjell View Post

                      Sure? Most people tend to get discouraged when everything isn't pre-configured and handed to them on a silver platter.
                      ​I got better things to do with my time. Maybe you don't and that's the issue?

                      Comment

                      Working...
                      X