• iopq@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    I still don’t know what people use to create services other than systemd

    If you’re writing bash scripts you’re basically replicating a lot of the functionality of systemd but with larger foot guns

    • unhrpetby@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months ago

      We can use dinit, s6, runit, and openrc.

      There are more, but these are all top contenders.

      I switched to dinit recently, it uses declarative service management (like systemd unit files). Very clean, fast, lightweight, and portable.

      • jim3692@discuss.online
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        5 months ago

        Maybe the arguments against systemd are issues of the past. I see people, hating systemd, bringing the same arguments of it being unstable, or constantly breaking, again and again.

        However, I don’t remember actually coming across any of those problems, or discussions about them, for the past 5+ years that I have been using Linux both for my computers and servers.

        I have used Ubuntu, Debian, Fedora, Arch, Proxmox, NixOS. All of them use systemd.

        They only problem I remember facing with systemd, which is actually never mentioned by anti-systemd people, is about its containers system, nspawn, which enables some security features by default. Those break things that tend to work with LXC without much tweaking. Docker, for example, may face issues running inside nspawn.

    • 9point6@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      The system V init approach did the job fine for a couple of decades—even if the actual service definitions were a glorified shell switch statement as you insinuate.

      Canonical did their upstart thing for a couple of years that wasn’t too bad to use, personally I’m glad they ended up switching to systemd though.