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.
Love me some systemd timers. Much more fun than cron.
Sane handling of environment variables with EnvironmentFile=
Out of the box logging. Especially useful is the ability to journalctl -f to watch long-running processes, which I’m not sure whether possible with cron
The ability to trigger the service manually rather than setting the timer to * * * * *, then forgetting it’s supposed to run in a minute, get distracted, come back in 15 minutes
My only complaint is it’s a bit verbose. I’d rather have it as an option inside the .service file. The .timer requires some boilerplate like [Unit].description (it… uh… triggers a service. that’s the description), and WantedBy=timers.target. But these are small prices to pay
My only complaint is it’s a bit verbose. I’d rather have it as an option inside the .service file. The .timer requires some boilerplate like [Unit].description (it… uh… triggers a service. that’s the description), and WantedBy=timers.target.
This can be solved through abstraction and automation.
In NixOS for example, you can declare a service that runs an arbitrary script every day like this:
This automatically creates a service file with the script in its ExecStart and an accompanying timer which runs daily and is part of the timers.target.
Yep, I manage my servers and local machine with Ansible so I abstracted it with a role. This is indeed not that bad of a con because it’s still plaintext so automation is easy, but it’s still a minor issue ;)
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Love me some systemd timers. Much more fun than cron.
EnvironmentFile=journalctl -fto watch long-running processes, which I’m not sure whether possible with cron* * * * *, then forgetting it’s supposed to run in a minute, get distracted, come back in 15 minutesMy only complaint is it’s a bit verbose. I’d rather have it as an option inside the
.servicefile. The.timerrequires some boilerplate like[Unit].description(it… uh… triggers a service. that’s the description), andWantedBy=timers.target. But these are small prices to payAnother thing I particularly like is
systemctl list-timers --alland its overview of the timer statuses and when they’re going to run next.This can be solved through abstraction and automation.
In NixOS for example, you can declare a service that runs an arbitrary script every day like this:
This automatically creates a service file with the script in its
ExecStartand an accompanying timer which runs daily and is part of thetimers.target.Yep, I manage my servers and local machine with Ansible so I abstracted it with a role. This is indeed not that bad of a con because it’s still plaintext so automation is easy, but it’s still a minor issue ;)