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
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.
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.
News
-
Linux Servers Targeted by Akira Ransomware
A group of bad actors who have already extorted $42 million have their sights set on the Linux platform.
-
TUXEDO Computers Unveils Linux Laptop Featuring AMD Ryzen CPU
This latest release is the first laptop to include the new CPU from Ryzen and Linux preinstalled.
-
XZ Gets the All-Clear
The back door xz vulnerability has been officially reverted for Fedora 40 and versions 38 and 39 were never affected.
-
Canonical Collaborates with Qualcomm on New Venture
This new joint effort is geared toward bringing Ubuntu and Ubuntu Core to Qualcomm-powered devices.
-
Kodi 21.0 Open-Source Entertainment Hub Released
After a year of development, the award-winning Kodi cross-platform, media center software is now available with many new additions and improvements.
-
Linux Usage Increases in Two Key Areas
If market share is your thing, you'll be happy to know that Linux is on the rise in two areas that, if they keep climbing, could have serious meaning for Linux's future.
-
Vulnerability Discovered in xz Libraries
An urgent alert for Fedora 40 has been posted and users should pay attention.
-
Canonical Bumps LTS Support to 12 years
If you're worried that your Ubuntu LTS release won't be supported long enough to last, Canonical has a surprise for you in the form of 12 years of security coverage.
-
Fedora 40 Beta Released Soon
With the official release of Fedora 40 coming in April, it's almost time to download the beta and see what's new.
-
New Pentesting Distribution to Compete with Kali Linux
SnoopGod is now available for your testing needs