this post was submitted on 16 Dec 2024
78 points (89.8% liked)
Linux
48669 readers
429 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Maybe tangential but this reminded me of how much I hate setting up systemd timers/services. I refuse to accept that creating two files in two different directories and searching online for the default timer and service templates is an okay workflow over simply throwing a cron expression next to the command you want to run and being done with it. Is there really no way we can have a crontab-equivalent that virtually converts into a systemd backend when you don't need the extra power? I feel like an old person that can't accept change but it's been a decade and I'm still angry.
This is a configuration declaration abstraction issue. Systemd timers and services are more like primitives.
In NixOS, we have an abstraction that allows simple declaration of a service and timer that runs some script.
As an example, I use this to export my paperless for backup daily in a way that is safe (paperless itself cannot run during that time, guaranteed by systemd) and simple:
https://github.com/Atemu/nixos-config/blob/ca0d39eb98c62424208487f973573478268048b4/modules/paperless/module.nix#L59-L95
(Even without NixOS domain knowledge you should be able to follow what's going on here.)
All that's needed in order to cause a systemd timer to be created for this service is to declare the
startAt = "daily";at the bottom.I love this, I have nixos on my server and it handles all the services this way
I did this for awhile...
https://github.com/systemd-cron/systemd-cron-next
If I remember whatever chef script I was blowing out mucked up something enough I ended up ditching it and manually rebuilding the timers as sysd units.
Even as someone who likes systemd since trying to teach init is pretty uniquely awful, I still have a load of one a year cron jobs I just use a BSD box for.