• Azzu@lemm.ee
      link
      fedilink
      arrow-up
      12
      arrow-down
      1
      ·
      edit-2
      2 days ago

      systemd moment in the sense that someone not affiliated with systemd used systemd to write a stop job that doesn’t terminate quickly? Or that you willingly installed software that brought along a slow stop job with it?

      This is like so far away from systemd’s fault, idk, it must just be a meme right?

      • juipeltje@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        2 days ago

        Pretty sure i’ve had this happen with services i didn’t even create, but yeah it was just a joke, i don’t care about init systems, but i don’t recall this ever happening when i was using runit.

        • Azzu@lemm.ee
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          edit-2
          2 days ago

          I don’t know runit. Maybe runit didn’t even have a way to delay or customize shutdown, maybe it always just waits 5 seconds and then forcibly terminates a process, resulting in you never noticing when a cleanup job was too slow. Maybe you just randomly never installed a particular program with a slow shutdown job while using runit. There’s a bunch of reasonable explanations and possibilities for why this difference exists, and they can all mean systemd is perfectly reasonable.

          • juipeltje@lemmy.world
            link
            fedilink
            arrow-up
            3
            arrow-down
            1
            ·
            2 days ago

            Alright man, fact remains i was just making a silly joke, you don’t have to be poettering’s pr team lol

            • Azzu@lemm.ee
              link
              fedilink
              arrow-up
              2
              arrow-down
              2
              ·
              2 days ago

              You’re the one who brought up runit and insinuated it doesn’t have this problem ¯_(ツ)_/¯