Systemd/timers - Revision history

MoltenMonster: https://man.archlinux.org/man/systemd.timer.5.en "services with RemainAfterExit=yes set (which stay around continuously even after the service's main process exited) are usually not suitable for activation via repetitive timers, as they will only be activated once, and then stay around forever."

2025-11-26T21:08:13Z

https://man.archlinux.org/man/systemd.timer.5.en "services with RemainAfterExit=yes set (which stay around continuously even after the service's main process exited) are usually not suitable for activation via repetitive timers, as they will only be activated once, and then stay around forever."

← Older revision		Revision as of 21:08, 26 November 2025
Line 35:		Line 35:
	Type = "oneshot";		Type = "oneshot";
	User = "root";		User = "root";
	RemainAfterExit = true; # Prevents the service from automatically starting on rebuild. See https://discourse.nixos.org/t/how-to-prevent-custom-systemd-service-from-restarting-on-nixos-rebuild-switch/43431
	};		};
	};		};

Thomas131: Added `RemainAfterExit = true;` to the example since this is probably what people want.

2025-06-02T16:29:12Z

Added `RemainAfterExit = true;` to the example since this is probably what people want.

← Older revision		Revision as of 16:29, 2 June 2025
Line 35:		Line 35:
	Type = "oneshot";		Type = "oneshot";
	User = "root";		User = "root";
			RemainAfterExit = true; # Prevents the service from automatically starting on rebuild. See https://discourse.nixos.org/t/how-to-prevent-custom-systemd-service-from-restarting-on-nixos-rebuild-switch/43431
	};		};
	};		};

Thefossguy: Added the use of `OnCalendar` option in the example of `systemd.timers` and add a section on verifying the calendar event by getting next _N_ times when the calendar event would occur.

2024-12-07T04:06:05Z

Added the use of `OnCalendar` option in the example of `systemd.timers` and add a section on verifying the calendar event by getting next _N_ times when the calendar event would occur.

@@ Line 12: / Line 12: @@
 The following example timer runs a systemd unit every 5 minutes which invokes a bash script.
 </translate>
-<syntaxHighlight lang="nix">
+<syntaxhighlight lang="nix">
 systemd.timers."hello-world" = {
    wantedBy = [ "timers.target" ];
@@ Line 18: / Line 18: @@
        OnBootSec = "5m";
        OnUnitActiveSec = "5m";
        Unit = "hello-world.service";
      };
@@ Line 32: / Line 37: @@
    };
 };
-</syntaxHighlight>
+</syntaxhighlight>
@@ Line 46: / Line 51: @@
 </syntaxhighlight>
 in your terminal.
 ====Using the <code>systemd.services.&lt;name&gt;.startAt</code> shorthand====

H7x4: Add section about systemd.services..startAt

2024-09-15T22:55:53Z

Add section about systemd.services.<name>.startAt

@@ Line 45: / Line 45: @@
 foo command-options
 </syntaxhighlight>
 in your terminal.
 ====Running timer on a schedule====

Ziasquinn: added alternative example of the call for the binary and command, the quotes confused me when replicating this for rclone (maybe more me but didn't seem like it hurt to add)

2024-09-15T17:39:15Z

added alternative example of the call for the binary and command, the quotes confused me when replicating this for rclone (maybe more me but didn't seem like it hurt to add)

@@ Line 33: / Line 33: @@
 };
 </syntaxHighlight>
 <translate>
 <!--T:4-->

Unabomberlive: Marked this version for translation

2024-08-06T07:03:27Z

Marked this version for translation

← Older revision		Revision as of 07:03, 6 August 2024
Line 2:		Line 2:

	<translate>		<translate>
			<!--T:1-->
	Timers are systemd unit files whose name ends in .timer that control .service files or events. Timers can be used as an alternative to <code>cron</code>. Timers have built-in support for calendar-based events and monotonic time events, and can be run asynchronously.		Timers are systemd unit files whose name ends in .timer that control .service files or events. Timers can be used as an alternative to <code>cron</code>. Timers have built-in support for calendar-based events and monotonic time events, and can be run asynchronously.
	</translate>		</translate>
	<translate>		<translate>
	== Configuration ==		== Configuration == <!--T:2-->
	</translate>		</translate>
	<translate>		<translate>
			<!--T:3-->
	The following example timer runs a systemd unit every 5 minutes which invokes a bash script.		The following example timer runs a systemd unit every 5 minutes which invokes a bash script.
	</translate>		</translate>
Line 32:		Line 34:
	</syntaxHighlight>		</syntaxHighlight>
	<translate>		<translate>
			<!--T:4-->
	The following example starts once a day (at 12:00am). When activated, it triggers the service immediately if it missed the last start time (option Persistent=true), for example due to the system being powered off.		The following example starts once a day (at 12:00am). When activated, it triggers the service immediately if it missed the last start time (option Persistent=true), for example due to the system being powered off.
	</translate>		</translate>
Line 43:		Line 46:
	</syntaxHighlight>		</syntaxHighlight>
	<translate>		<translate>
			<!--T:5-->
	More examples can be found at the [https://wiki.archlinux.org/title/Systemd/Timers Arch Wiki] and at the <code>systemd.timer</code> manpage.		More examples can be found at the [https://wiki.archlinux.org/title/Systemd/Timers Arch Wiki] and at the <code>systemd.timer</code> manpage.
	</translate>		</translate>
	<translate>		<translate>
	== Usage ==		== Usage == <!--T:6-->
	</translate>		</translate>
	<translate>		<translate>
			<!--T:7-->
	List active timers and their current state:		List active timers and their current state:
	</translate>		</translate>
Line 55:		Line 60:
	</syntaxhighlight>		</syntaxhighlight>
	<translate>		<translate>
			<!--T:8-->
	Manually run a service once for testing purposes:		Manually run a service once for testing purposes:
	</translate>		</translate>

Unabomberlive: Make page translatable

2024-08-06T07:03:16Z

Make page translatable

← Older revision		Revision as of 07:03, 6 August 2024
Line 1:		Line 1:
	{{Systemd/breadcrumb}}		{{Systemd/breadcrumb}}

	Timers are systemd unit files whose name ends in .timer that control .service files or events. Timers can be used as an alternative to <code>cron</code>. Timers have built-in support for calendar-based events and monotonic time events, and can be run asynchronously.		<translate>
			Timers are systemd unit files whose name ends in .timer that control .service files or events. Timers can be used as an alternative to <code>cron</code>. Timers have built-in support for calendar-based events and monotonic time events, and can be run asynchronously.
			</translate>
			<translate>
	== Configuration ==		== Configuration ==
			</translate>
			<translate>
	The following example timer runs a systemd unit every 5 minutes which invokes a bash script.		The following example timer runs a systemd unit every 5 minutes which invokes a bash script.
			</translate>
	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
	systemd.timers."hello-world" = {		systemd.timers."hello-world" = {
Line 28:		Line 31:
	};		};
	</syntaxHighlight>		</syntaxHighlight>
			<translate>
	The following example starts once a day (at 12:00am). When activated, it triggers the service immediately if it missed the last start time (option Persistent=true), for example due to the system being powered off.		The following example starts once a day (at 12:00am). When activated, it triggers the service immediately if it missed the last start time (option Persistent=true), for example due to the system being powered off.
			</translate>
	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
	...		...
Line 39:		Line 42:
	};		};
	</syntaxHighlight>		</syntaxHighlight>
			<translate>
	More examples can be found at the [https://wiki.archlinux.org/title/Systemd/Timers Arch Wiki] and at the <code>systemd.timer</code> manpage.		More examples can be found at the [https://wiki.archlinux.org/title/Systemd/Timers Arch Wiki] and at the <code>systemd.timer</code> manpage.
			</translate>
			<translate>
	== Usage ==		== Usage ==
			</translate>
			<translate>
	List active timers and their current state:		List active timers and their current state:
			</translate>
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	systemctl list-timers		systemctl list-timers
	</syntaxhighlight>		</syntaxhighlight>
			<translate>
	Manually run a service once for testing purposes:		Manually run a service once for testing purposes:
			</translate>
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	systemctl start hello-world		systemctl start hello-world
	</syntaxhighlight>		</syntaxhighlight>
	[[Category:systemd]]		[[Category:systemd]]

Klinger: Category:systemd

2024-04-24T21:35:48Z

Category:systemd

← Older revision		Revision as of 21:35, 24 April 2024
Line 55:		Line 55:
	systemctl start hello-world		systemctl start hello-world
	</syntaxhighlight>		</syntaxhighlight>
			[[Category:systemd]]

0x4A6F: 0x4A6F moved page Systemd/Timers to Systemd/timers

2024-04-03T18:41:08Z

0x4A6F moved page Systemd/Timers to Systemd/timers

← Older revision	Revision as of 18:41, 3 April 2024
(No difference)

0x4A6F at 18:28, 3 April 2024

2024-04-03T18:28:31Z

← Older revision		Revision as of 18:28, 3 April 2024
Line 1:		Line 1:
			{{Systemd/breadcrumb}}

	Timers are systemd unit files whose name ends in .timer that control .service files or events. Timers can be used as an alternative to <code>cron</code>. Timers have built-in support for calendar-based events and monotonic time events, and can be run asynchronously.		Timers are systemd unit files whose name ends in .timer that control .service files or events. Timers can be used as an alternative to <code>cron</code>. Timers have built-in support for calendar-based events and monotonic time events, and can be run asynchronously.