They sure are, and it makes me happy to see you enjoy learning... so...Raspberry Pi's are fun
Let me introduce you to the world of systemd.timers, an alternative to cron.
Here is an old tutorial to start you out, then venture out into the interweb and keep learning:
https://opensource.com/article/20/7/systemd-timers
As mentioned in the great Arch wiki there are both up and downsides:
Other good links to read for learning:Benefits
The main benefits of using timers come from each job having its own systemd service. Some of these benefits are:
Jobs can be easily started independently of their timers. This simplifies debugging.
Each job can be configured to run in a specific environment (see systemd.exec(5)).
Jobs can be attached to cgroups.
Jobs can be set up to depend on other systemd units.
Jobs are logged in the systemd journal for easy debugging.
Caveats
Some things that are easy to do with cron are difficult to do with timer units alone:
Creation: to set up a timed job with systemd you need to create two files and run systemctl commands, compared to adding a single line to a crontab.
Emails: there is no built-in equivalent to cron's MAILTO for sending emails on job failure. See #MAILTO for an example of setting up a similar functionality using OnFailure=.
Also note that user timer units will only run during an active user login session by default. However, lingering can enable services to run at boot even when the user has no active login session.
https://askubuntu.com/questions/1083537 ... nd-service
https://www.freedesktop.org/software/sy ... timer.html
I'm not saying you SHOULD change anything on your setup, but you seem to enjoy learning.
Statistics: Posted by bedna — Thu May 09, 2024 7:08 am