waldek
/
linux_course_doc
1
0
Fork 0
Code Issues 2 Pull Requests Projects Releases Wiki Activity

fixes quote

This commit is contained in:
waldek 2021-08-15 22:48:02 +02:00
parent 094d670c5b
commit a27d77bdcd
1 changed files with 15 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
modules/qualifying/learning_systemd.md
View File

@ -543,21 +543,25 @@ If you now watch your log in real time with `journalctl -f --user-unit monitor.s
The following advice was taken from the arch [wiki](https://wiki.archlinux.org/title/Systemd/Timers). The following advice was taken from the arch [wiki](https://wiki.archlinux.org/title/Systemd/Timers).
>As a cron replacement #### As a cron replacement
Although cron is arguably the most well-known job scheduler, systemd timers can be an alternative. Although cron is arguably the most well-known job scheduler, systemd timers can be an alternative.
>Benefits ##### Benefits
The main benefits of using timers come from each job having its own systemd service. Some of these benefits are: 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. * 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)). * Each job can be configured to run in a specific environment (see systemd.exec(5)).
Jobs can be attached to cgroups. * Jobs can be attached to cgroups.
Jobs can be set up to depend on other systemd units. * Jobs can be set up to depend on other systemd units.
Jobs are logged in the systemd journal for easy debugging. * Jobs are logged in the systemd journal for easy debugging.
Caveats
##### Caveats
Some things that are easy to do with cron are difficult to do with timer units alone: 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. * 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 the next section for an example of setting up a similar functionality using OnFailure=. * Emails: there is no built-in equivalent to cron's MAILTO for sending emails on job failure. See the next section 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.
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.