Systemd/User Services - Revision history

Crasm: Added section clarifying linger settings and systemd's user management service

2025-12-10T08:28:16Z

Added section clarifying linger settings and systemd's user management service

← Older revision		Revision as of 08:28, 10 December 2025
Line 32:		Line 32:
	By default, user services will be stopped when the user logs out and will start again when the user logs back in due to us setting {{ic\|<nowiki>wantedBy = [ "default.target" ]</nowiki>}} in the example.		By default, user services will be stopped when the user logs out and will start again when the user logs back in due to us setting {{ic\|<nowiki>wantedBy = [ "default.target" ]</nowiki>}} in the example.

	== ~~Keeping~~ user ~~services running after logout~~ == <!--T:7-->		== Enabling the user management service and user process lingering == <!--T:7-->

			Without the user management unit {{ic\|user@.service}}, commands such as {{ic\|systemctl --user}} will fail, and configured options under {{ic\|systemd.user}} will not take effect. This is typically observed on minimal systems without a desktop environment.

			When lingering is enabled for a user, the user management service is spawned at boot and can run services independently of the user's session, including keeping services running after a user logs out.

	<!--T:8-->		<!--T:8-->
	~~If you need a user service to stay running after a user logs out, you need to~~ enable "[https://search.nixos.org/options?channel=unstable&show=users.users.%3Cname%3E.linger&from=0&size=50&sort=relevance&type=packages&query=users.users.%3Cname%3E.linger lingering]" by setting {{ic\|<nowiki>users.users.<username>.linger = true;</nowiki>}}		You can enable "[https://search.nixos.org/options?channel=unstable&show=users.users.%3Cname%3E.linger&from=0&size=50&sort=relevance&type=packages&query=users.users.%3Cname%3E.linger lingering]" by setting {{ic\|<nowiki>users.users.<username>.linger = true;</nowiki>}} or running {{ic\|sudo loginctl enable-linger [USER...]}}.

	<!--T:9-->		<!--T:9-->
	~~You'll also likely want~~ to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} ~~so the service starts at boot time~~.		For a user service to start at boot, change the service configuration to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}}.

	== Enabling a service for specific users == <!--T:10-->		== Enabling a service for specific users == <!--T:10-->

Ardenet: Marked this version for translation

2025-10-07T22:41:19Z

Marked this version for translation

← Older revision		Revision as of 22:41, 7 October 2025
Line 40:		Line 40:
	You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.		You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.

	== Enabling a service for specific users ==		== Enabling a service for specific users == <!--T:10-->

			<!--T:11-->
	By default, enabling a user service enables it for every user for which systemd spawns a service manager. If you wish for the service to be run only for specific users (say, {{ic\|<nowiki>UserA</nowiki>}} and {{ic\|<nowiki>UserB</nowiki>}}), use {{ic\|<nowiki>ConditionUser</nowiki>}} ({{ic\|<nowiki>man 5 systemd.unit</nowiki>}}):		By default, enabling a user service enables it for every user for which systemd spawns a service manager. If you wish for the service to be run only for specific users (say, {{ic\|<nowiki>UserA</nowiki>}} and {{ic\|<nowiki>UserB</nowiki>}}), use {{ic\|<nowiki>ConditionUser</nowiki>}} ({{ic\|<nowiki>man 5 systemd.unit</nowiki>}}):
	</translate>		</translate>
Line 52:		Line 53:

	<translate>		<translate>
			<!--T:12-->
	Likewise, you can also disable a service for a specific user:		Likewise, you can also disable a service for a specific user:
	</translate>		</translate>
Line 62:		Line 64:

	<translate>		<translate>
	== Usage ==		== Usage == <!--T:13-->

			<!--T:14-->
	To interact with user-specific systemd services, use the <code>--user</code> flag with the <code>systemctl</code> command. For example, to check the status of a user service:		To interact with user-specific systemd services, use the <code>--user</code> flag with the <code>systemctl</code> command. For example, to check the status of a user service:
	</translate>		</translate>
Line 70:		Line 73:

	<translate>		<translate>
			<!--T:15-->
	To view logs for a specific user service, use <code>journalctl</code> with the <code>--user-unit</code> option:		To view logs for a specific user service, use <code>journalctl</code> with the <code>--user-unit</code> option:
	</translate>		</translate>
Line 76:		Line 80:

	<translate>		<translate>
			<!--T:16-->
	To list all active user units:		To list all active user units:
	</translate>		</translate>
Line 82:		Line 87:

	<translate>		<translate>
			<!--T:17-->
	[[Category:systemd]]		[[Category:systemd]]
	</translate>		</translate>

Ardenet: repositon translate tag

2025-10-07T22:40:45Z

repositon translate tag

← Older revision		Revision as of 22:40, 7 October 2025
Line 4:		Line 4:
	<!--T:1-->		<!--T:1-->
	Systemd supports running a separate instance of systemd for a given user, allowing the user to control their own services. See here for more information: https://wiki.archlinux.org/title/Systemd/User		Systemd supports running a separate instance of systemd for a given user, allowing the user to control their own services. See here for more information: https://wiki.archlinux.org/title/Systemd/User
	~~</translate>~~
	~~<translate>~~
	<!--T:2-->		<!--T:2-->
	In NixOS, a user service can be expressed with {{ic\|systemd.user.services.<name>}}, as documented here: https://search.nixos.org/options?query=systemd.user.services		In NixOS, a user service can be expressed with {{ic\|systemd.user.services.<name>}}, as documented here: https://search.nixos.org/options?query=systemd.user.services
	~~</translate>~~
	~~<translate>~~
	<!--T:3-->		<!--T:3-->
	This may be useful if you want a user to be able to start, stop, and restart their own instance of a service without needing to make the user a sudoer.		This may be useful if you want a user to be able to start, stop, and restart their own instance of a service without needing to make the user a sudoer.
	~~</translate>~~
	~~<translate>~~
	<!--T:4-->		<!--T:4-->
	Here is an example:		Here is an example:
	</translate>		</translate>
	~~<translate>~~
	~~<!--T:5-->~~
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	systemd.user.services.my-cool-user-service = {		systemd.user.services.my-cool-user-service = {
Line 31:		Line 27:
	};		};
	</syntaxhighlight>		</syntaxhighlight>
	~~</translate>~~
	<translate>		<translate>
	<!--T:6-->		<!--T:6-->
	By default, user services will be stopped when the user logs out and will start again when the user logs back in due to us setting {{ic\|<nowiki>wantedBy = [ "default.target" ]</nowiki>}} in the example.		By default, user services will be stopped when the user logs out and will start again when the user logs back in due to us setting {{ic\|<nowiki>wantedBy = [ "default.target" ]</nowiki>}} in the example.
	~~</translate>~~
	~~<translate>~~
	== Keeping user services running after logout == <!--T:7-->		== Keeping user services running after logout == <!--T:7-->
	~~</translate>~~
	~~<translate>~~
	<!--T:8-->		<!--T:8-->
	If you need a user service to stay running after a user logs out, you need to enable "[https://search.nixos.org/options?channel=unstable&show=users.users.%3Cname%3E.linger&from=0&size=50&sort=relevance&type=packages&query=users.users.%3Cname%3E.linger lingering]" by setting {{ic\|<nowiki>users.users.<username>.linger = true;</nowiki>}}		If you need a user service to stay running after a user logs out, you need to enable "[https://search.nixos.org/options?channel=unstable&show=users.users.%3Cname%3E.linger&from=0&size=50&sort=relevance&type=packages&query=users.users.%3Cname%3E.linger lingering]" by setting {{ic\|<nowiki>users.users.<username>.linger = true;</nowiki>}}
	~~</translate>~~
	~~<translate>~~
	<!--T:9-->		<!--T:9-->
	You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.		You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.
	~~</translate>~~
	== Enabling a service for specific users ==		== Enabling a service for specific users ==

	By default, enabling a user service enables it for every user for which systemd spawns a service manager. If you wish for the service to be run only for specific users (say, {{ic\|<nowiki>UserA</nowiki>}} and {{ic\|<nowiki>UserB</nowiki>}}), use {{ic\|<nowiki>ConditionUser</nowiki>}} ({{ic\|<nowiki>man 5 systemd.unit</nowiki>}}):		By default, enabling a user service enables it for every user for which systemd spawns a service manager. If you wish for the service to be run only for specific users (say, {{ic\|<nowiki>UserA</nowiki>}} and {{ic\|<nowiki>UserB</nowiki>}}), use {{ic\|<nowiki>ConditionUser</nowiki>}} ({{ic\|<nowiki>man 5 systemd.unit</nowiki>}}):
			</translate>

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	systemd.user.services.my-cool-user-service = {		systemd.user.services.my-cool-user-service = {
Line 55:		Line 51:
	</syntaxhighlight>		</syntaxhighlight>

			<translate>
	Likewise, you can also disable a service for a specific user:		Likewise, you can also disable a service for a specific user:
			</translate>

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
Line 63:		Line 61:
	</syntaxhighlight>		</syntaxhighlight>

			<translate>
	== Usage ==		== Usage ==

	To interact with user-specific systemd services, use the <code>--user</code> flag with the <code>systemctl</code> command. For example, to check the status of a user service:		To interact with user-specific systemd services, use the <code>--user</code> flag with the <code>systemctl</code> command. For example, to check the status of a user service:
			</translate>

	<syntaxhighlight lang="console"> $ systemctl --user status my-cool-user-service </syntaxhighlight>		<syntaxhighlight lang="console"> $ systemctl --user status my-cool-user-service </syntaxhighlight>

			<translate>
	To view logs for a specific user service, use <code>journalctl</code> with the <code>--user-unit</code> option:		To view logs for a specific user service, use <code>journalctl</code> with the <code>--user-unit</code> option:
			</translate>

	<syntaxhighlight lang="console"> $ journalctl --user-unit my-cool-user-service </syntaxhighlight>		<syntaxhighlight lang="console"> $ journalctl --user-unit my-cool-user-service </syntaxhighlight>

			<translate>
	To list all active user units:		To list all active user units:
			</translate>

	<syntaxhighlight lang="console"> $ systemctl --user list-units </syntaxhighlight>		<syntaxhighlight lang="console"> $ systemctl --user list-units </syntaxhighlight>

			<translate>
	[[Category:systemd]]		[[Category:systemd]]
			</translate>

Pigs: Add usage section

2025-05-22T18:14:06Z

Add usage section

@@ Line 54: / Line 54: @@
 };
 </syntaxhighlight>
 [[Category:systemd]]

Colinsane: show how to enable a service for only specific users

2024-10-10T20:59:17Z

show how to enable a service for only specific users

← Older revision		Revision as of 20:59, 10 October 2024
Line 47:		Line 47:
	You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.		You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.
	</translate>		</translate>
			== Enabling a service for specific users ==
			By default, enabling a user service enables it for every user for which systemd spawns a service manager. If you wish for the service to be run only for specific users (say, {{ic\|<nowiki>UserA</nowiki>}} and {{ic\|<nowiki>UserB</nowiki>}}), use {{ic\|<nowiki>ConditionUser</nowiki>}} ({{ic\|<nowiki>man 5 systemd.unit</nowiki>}}):
			<syntaxhighlight lang="nix">
			systemd.user.services.my-cool-user-service = {
			unitConfig.ConditionUser = "UserA\|UserB";
			};
			</syntaxhighlight>
	[[Category:systemd]]		[[Category:systemd]]

Unabomberlive at 08:28, 8 August 2024

2024-08-08T08:28:36Z

← Older revision		Revision as of 08:28, 8 August 2024
Line 1:		Line 1:
			{{Systemd/breadcrumb}}

	<translate>		<translate>
	<!--T:1-->		<!--T:1-->

Unabomberlive: Marked this version for translation

2024-08-05T16:42:38Z

Marked this version for translation

← Older revision		Revision as of 16:42, 5 August 2024
Line 1:		Line 1:
	<translate>		<translate>
			<!--T:1-->
	Systemd supports running a separate instance of systemd for a given user, allowing the user to control their own services. See here for more information: https://wiki.archlinux.org/title/Systemd/User		Systemd supports running a separate instance of systemd for a given user, allowing the user to control their own services. See here for more information: https://wiki.archlinux.org/title/Systemd/User
	</translate>		</translate>
	<translate>		<translate>
			<!--T:2-->
	In NixOS, a user service can be expressed with {{ic\|systemd.user.services.<name>}}, as documented here: https://search.nixos.org/options?query=systemd.user.services		In NixOS, a user service can be expressed with {{ic\|systemd.user.services.<name>}}, as documented here: https://search.nixos.org/options?query=systemd.user.services
	</translate>		</translate>
	<translate>		<translate>
			<!--T:3-->
	This may be useful if you want a user to be able to start, stop, and restart their own instance of a service without needing to make the user a sudoer.		This may be useful if you want a user to be able to start, stop, and restart their own instance of a service without needing to make the user a sudoer.
	</translate>		</translate>
	<translate>		<translate>
			<!--T:4-->
	Here is an example:		Here is an example:
	</translate>		</translate>
	<translate>		<translate>
			<!--T:5-->
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	systemd.user.services.my-cool-user-service = {		systemd.user.services.my-cool-user-service = {
Line 26:		Line 31:
	</translate>		</translate>
	<translate>		<translate>
			<!--T:6-->
	By default, user services will be stopped when the user logs out and will start again when the user logs back in due to us setting {{ic\|<nowiki>wantedBy = [ "default.target" ]</nowiki>}} in the example.		By default, user services will be stopped when the user logs out and will start again when the user logs back in due to us setting {{ic\|<nowiki>wantedBy = [ "default.target" ]</nowiki>}} in the example.
	</translate>		</translate>
	<translate>		<translate>
	== Keeping user services running after logout ==		== Keeping user services running after logout == <!--T:7-->
	</translate>		</translate>
	<translate>		<translate>
			<!--T:8-->
	If you need a user service to stay running after a user logs out, you need to enable "[https://search.nixos.org/options?channel=unstable&show=users.users.%3Cname%3E.linger&from=0&size=50&sort=relevance&type=packages&query=users.users.%3Cname%3E.linger lingering]" by setting {{ic\|<nowiki>users.users.<username>.linger = true;</nowiki>}}		If you need a user service to stay running after a user logs out, you need to enable "[https://search.nixos.org/options?channel=unstable&show=users.users.%3Cname%3E.linger&from=0&size=50&sort=relevance&type=packages&query=users.users.%3Cname%3E.linger lingering]" by setting {{ic\|<nowiki>users.users.<username>.linger = true;</nowiki>}}
	</translate>		</translate>
	<translate>		<translate>
			<!--T:9-->
	You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.		You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.
	</translate>		</translate>
	[[Category:systemd]]		[[Category:systemd]]

Unabomberlive at 16:42, 5 August 2024

2024-08-05T16:42:26Z

← Older revision		Revision as of 16:42, 5 August 2024
Line 1:		Line 1:
			<translate>
	Systemd supports running a separate instance of systemd for a given user, allowing the user to control their own services. See here for more information: https://wiki.archlinux.org/title/Systemd/User		Systemd supports running a separate instance of systemd for a given user, allowing the user to control their own services. See here for more information: https://wiki.archlinux.org/title/Systemd/User
			</translate>
			<translate>
	In NixOS, a user service can be expressed with {{ic\|systemd.user.services.<name>}}, as documented here: https://search.nixos.org/options?query=systemd.user.services		In NixOS, a user service can be expressed with {{ic\|systemd.user.services.<name>}}, as documented here: https://search.nixos.org/options?query=systemd.user.services
			</translate>
			<translate>
	This may be useful if you want a user to be able to start, stop, and restart their own instance of a service without needing to make the user a sudoer.		This may be useful if you want a user to be able to start, stop, and restart their own instance of a service without needing to make the user a sudoer.
			</translate>
			<translate>
	Here is an example:		Here is an example:
			</translate>
			<translate>
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	systemd.user.services.my-cool-user-service = {		systemd.user.services.my-cool-user-service = {
Line 19:		Line 24:
	};		};
	</syntaxhighlight>		</syntaxhighlight>
			</translate>
			<translate>
	By default, user services will be stopped when the user logs out and will start again when the user logs back in due to us setting {{ic\|<nowiki>wantedBy = [ "default.target" ]</nowiki>}} in the example.		By default, user services will be stopped when the user logs out and will start again when the user logs back in due to us setting {{ic\|<nowiki>wantedBy = [ "default.target" ]</nowiki>}} in the example.
			</translate>
			<translate>
	== Keeping user services running after logout ==		== Keeping user services running after logout ==
			</translate>
			<translate>
	If you need a user service to stay running after a user logs out, you need to enable "[https://search.nixos.org/options?channel=unstable&show=users.users.%3Cname%3E.linger&from=0&size=50&sort=relevance&type=packages&query=users.users.%3Cname%3E.linger lingering]" by setting {{ic\|<nowiki>users.users.<username>.linger = true;</nowiki>}}		If you need a user service to stay running after a user logs out, you need to enable "[https://search.nixos.org/options?channel=unstable&show=users.users.%3Cname%3E.linger&from=0&size=50&sort=relevance&type=packages&query=users.users.%3Cname%3E.linger lingering]" by setting {{ic\|<nowiki>users.users.<username>.linger = true;</nowiki>}}
			</translate>
			<translate>
	You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.		You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.
			</translate>
	[[Category:systemd]]		[[Category:systemd]]

Denperidge: Modified NixOS Search link to not specify channel=unstable. This way the default option for the website will be selected, which should usually be the latest default NixOS channel. Might be more in tune with user expectancy, as people using unstable are advanced enough to select the channel manually

2024-06-18T13:11:39Z

Modified NixOS Search link to not specify channel=unstable. This way the default option for the website will be selected, which should usually be the latest default NixOS channel. Might be more in tune with user expectancy, as people using unstable are advanced enough to select the channel manually

← Older revision		Revision as of 13:11, 18 June 2024
Line 1:		Line 1:
	Systemd supports running a separate instance of systemd for a given user, allowing the user to control their own services. See here for more information: https://wiki.archlinux.org/title/Systemd/User		Systemd supports running a separate instance of systemd for a given user, allowing the user to control their own services. See here for more information: https://wiki.archlinux.org/title/Systemd/User

	In NixOS, a user service can be expressed with {{ic\|systemd.user.services.<name>}}, as documented here: https://search.nixos.org/options?~~channel=unstable&~~query=systemd.user.services		In NixOS, a user service can be expressed with {{ic\|systemd.user.services.<name>}}, as documented here: https://search.nixos.org/options?query=systemd.user.services

	This may be useful if you want a user to be able to start, stop, and restart their own instance of a service without needing to make the user a sudoer.		This may be useful if you want a user to be able to start, stop, and restart their own instance of a service without needing to make the user a sudoer.

Klinger: Category:systemd

2024-04-24T21:36:12Z

Category:systemd

← Older revision		Revision as of 21:36, 24 April 2024
Line 27:		Line 27:

	You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.		You'll also likely want to change to {{ic\|<nowiki>wantedBy = [ "multi-user.target" ];</nowiki>}} so the service starts at boot time.
			[[Category:systemd]]