324
Systemd: Hidden Gems for a Better Linux (tadeubento.com)
submitted 3 years ago by to c/linux@lemmy.ml
90 comments fedilink hide all child comments
 

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. :)

you are viewing a single comment's thread
view the rest of the comments
[–] 29 points 3 years ago (2 children)

Finally a systemd praise post after so many hateful remarks. I knew systemd could do dns resolving but just learned it could handle the entire network stack and replace NetworkManager. I have a question: How can services such as Apache adapt to both NM and systemd at the same time? NM and systemd have different wait-online services. You can also add systemd-analyze for boot time analysis to the list.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 5 points 3 years ago*

    How can services such as Apache adapt to both NM and systemd at the same time? NM and systemd have different wait-online services

    If you look at the systemd unit for Apache you'll just find After=network.target - it doesn't wait-online at all. Apache doesn't really care if you're using NM or systemd-networkd, it simply queries the system (like the ip command does) to know what's going on with the network. It was designed as recommended for moderns programs: it is aware that your network might change and listens for the appropriate signals and takes care of the binds dynamically.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 3 years ago*

    I knew systemd could do dns resolving but just learned it could handle the entire network stack and replace NetworkManager.

    It depends on your use case. I have three machines and use NetworkManager on one of them and systemd-networkd on the others. The latter is great for static configurations, but for a notebook that roams WiFi networks, it doesn't make the most sense.

  • permalink
  • fedilink
  • source
  • parent