Systemd is incredibly versatile and most people, including myself, are unaware of its full potential. Despite its usefulness, it is often overlooked due to controversy and the current state of things when it comes to software development. Begin today your journey thought Systemd's capabilities and discover how to efficiently manage systems with fewer processes than traditionally used.

After a few conversations with people on Lemmy and other places it became clear to me that most aren’t aware of what it can do and how much more robust it is compared to the usual “jankiness” we’re used to.

In this article I highlight less known features and give out a few practice examples on how to leverage Systemd to remove tons of redundant packages and processes.

And yes, Systemd does containers. :)

  • @ryannathans@lemmy.world
    -1•11 months ago

    All of this shit packed in is why it sucks. Do one thing and do it well. Try setting up a script to run on boot that doesn’t stop executing until you want to turn your pc off and watch all traces of sanity drain from your being. Now try it on freebsd. Much much easier

    • @exi@feddit.de
      7•11 months ago

      What’s the problem with that script? That’s such a basic use case and not very hard to do at all in systemd.

      Where do you struggle with it? Can we maybe help with something?

    • @TCB13@lemmy.worldOP
      6•11 months ago

      Did a couple of times, no issues. Simply add KillSignal=SIGINT or ExecStop=/bin/kill -s SIGINT -$MAINPID & /bin/kill -s SIGINT -$MAINPID and it will work out.