Love systemd timers
blog.tjll.net
Love systemd timers
1–10 of 309 posts
Re: Love systemd timers
#2I've been almost convinced by systemd (and have switched to using it), but God the syntax of those service files is so ugly ...
Re: Love systemd timers
#3I've been almost convinced by systemd (and have switched to using it), but God the syntax of those service files is so ugly ...
Could have been worse.
Could have been YAML.
Could have been XML.
Re: Love systemd timers
#4> humble systemd
Re: Love systemd timers
#5I've been almost convinced by systemd (and have switched to using it), but God the syntax of those service files is so ugly ...
Could have been worse. Could have been YAML. Could have been XML.
XML would have the advantage of having a grammar so we could validate the config files.
It would also make it much simpler to make good GUI editors for the files instead of the Notepad approach most unix config files take.
Re: Love systemd timers
#6Earlier quoted context omitted.
Could have been worse. Could have been YAML. Could have been XML.
XML would have the advantage of having a grammar so we could validate the config files. It would also make it much simpler to make good GUI editors for the files instead of the Notepad approach most unix config files take.
There are good GUI editors for XML?
Re: Love systemd timers
#7[deleted]
Re: Love systemd timers
#8I've been almost convinced by systemd (and have switched to using it), but God the syntax of those service files is so ugly ...
This is why I like NixOS. Defining systemd services in it is very neat.
Re: Love systemd timers
#9NixOS comes with systemd, so I've been using it as a first-class part of managing stuff. It's great, especially coming from macOS' launchd.
Which makes it nice to distribute a tool for NixOS so that it can lean into systemd instead of as some bolted-on afterthought.
Makes me wonder what you'd do if you were distributing a lifecycle-heavy tool for Linux users in general since systemd isn't ubiquitous.
I use a systemd timer to run a monthly scrub for my btrfs pool. Kinda cool how you can do increasingly useful things like skip the next scheduled event if the user initiates a scrub, do or don't accumulate tasks if you have a monthly task but the machine was offline for 6 months -- or fold them into a single task, etc.