Triggering regular tasks with Systemd
Winding Up the Clock
If you want Systemd to activate the timer directly at system startup, you need an [Install]
section in the timer unit. The WantedBy=
setting tells which other units the timer should start with. In Listing 2, the WantedBy=timers.target
setting ensures that Systemd starts the timer together with all other timers at the regular system startup time.
If you want Systemd to start the timer at startup time, you have to enable it explicitly (Listing 4, first line). Alternatively, you can start the timer manually (second line). All currently configured timers are listed by the systemctl list-timers
command (Figure 2).
Listing 4
Enabling at Startup
$ systemctl enable backup.timer $ systemctl start backup.timer
![](/var/linux_magazin/storage/images/issues/2018/214/systemd-timers/figure-2/732567-1-eng-US/Figure-2_large.png)
In the table under Next
, you can read when the system timer will execute the task the next time. The time remaining until then is in the Left
column. Similarly, you can see under Load
when systemd-timer
last executed the task. How long ago that was is shown in the Passed
column. Under Unit
, you will find the name of the corresponding timer and thus its configuration file.
You can end the display by pressing [Q]. By default, Systemctl only presents timers that are currently enabled. You can display the inactive timers on screen by appending the --all
parameter.
Snooze Button
If required, each timer can be stopped manually (Listing 5, first line) and disabled (second line). The manpage [1], which goes by the name of systemd.timer
, provides explanations for all presented settings. man systemd.time
provides further information on the format of dates and times and offers numerous additional examples.
Listing 5
Manual Stop
$ sudo systemctl stop my.timer $ sudo systemctl disable my.timer
Short-Term Alarm
If you want Systemd to make a single backup in exactly 30 minutes, use systemd-run
. The command looks like the first line of Listing 6. The /usr/bin/backup.sh /mnt
command appended there is executed by Systemd at the specified time. Use the parameter --on-active
to tell it the waiting time.
Listing 6
Examples
$ systemd-run --on-active=30m /usr/bin/backup.sh /mnt $ systemd-run --on-calendar=weekly --unit backup.service
The time units again correspond to those in Table 1. In the example, Systemd interprets the 30m
as half an hour. Alternatively, use --on-calendar=
to enter a specific date. The details are again provided in the same way as in the timer unit. With appropriate time specifications such as weekly
, the action can execute repeatedly.
In any case, systemd-run
creates a new timer in the background without you needing to create a service file (Figure 3). If a suitable service unit already exists, you can alternatively let systemd-run
launch it. To do this, simply pass in the name of the service unit using the --unit
parameter. The example from the second line of Listing 6 starts the task stored in the backup.service
service unit every week.
![](/var/linux_magazin/storage/images/issues/2018/214/systemd-timers/figure-3/732570-1-eng-US/Figure-3_large.png)
The timers generated by systemd-run
only exist temporarily. If you use the --on-active
parameter, the timer disappears immediately after the action has been executed; in any case, it disappears after rebooting the system. systemd-run
only creates a timer for a service unit if no suitable timer unit exists.
« Previous 1 2 3 4 Next »
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
![Learn More](https://www.linux-magazine.com/var/linux_magazin/storage/images/media/linux-magazine-eng-us/images/misc/learn-more/834592-1-eng-US/Learn-More_medium.png)
News
-
NVIDIA Released Driver for Upcoming NVIDIA 560 GPU for Linux
Not only has NVIDIA released the driver for its upcoming CPU series, it's the first release that defaults to using open-source GPU kernel modules.
-
OpenMandriva Lx 24.07 Released
If you’re into rolling release Linux distributions, OpenMandriva ROME has a new snapshot with a new kernel.
-
Kernel 6.10 Available for General Usage
Linus Torvalds has released the 6.10 kernel and it includes significant performance increases for Intel Core hybrid systems and more.
-
TUXEDO Computers Releases InfinityBook Pro 14 Gen9 Laptop
Sporting either AMD or Intel CPUs, the TUXEDO InfinityBook Pro 14 is an extremely compact, lightweight, sturdy powerhouse.
-
Google Extends Support for Linux Kernels Used for Android
Because the LTS Linux kernel releases are so important to Android, Google has decided to extend the support period beyond that offered by the kernel development team.
-
Linux Mint 22 Stable Delayed
If you're anxious about getting your hands on the stable release of Linux Mint 22, it looks as if you're going to have to wait a bit longer.
-
Nitrux 3.5.1 Available for Install
The latest version of the immutable, systemd-free distribution includes an updated kernel and NVIDIA driver.
-
Debian 12.6 Released with Plenty of Bug Fixes and Updates
The sixth update to Debian "Bookworm" is all about security mitigations and making adjustments for some "serious problems."
-
Canonical Offers 12-Year LTS for Open Source Docker Images
Canonical is expanding its LTS offering to reach beyond the DEB packages with a new distro-less Docker image.
-
Plasma Desktop 6.1 Released with Several Enhancements
If you're a fan of Plasma Desktop, you should be excited about this new point release.