What is the difference between systemd's user and system services?

--------------------------------------------------
Rise to the top 3% as a developer or hire one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------

Music by Eric Matyas
https://www.soundimage.org
Track title: Drifting Through My Dreams

--

Chapters
00:00 What Is The Difference Between Systemd'S User And System Services?
01:05 Accepted Answer Score 40
03:10 Thank you

--

Full question
https://superuser.com/questions/853717/w...

--

Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...

--

Tags
#linux #systemd

#avk47

ACCEPTED ANSWER

Score 40

You're a bit muddled, yes. ☺ You have:

A set of system services that are managed by the system-wide instance of systemd; which are each an instatiation of a template service unit in the file /etc/systemd/system/rt@.service.
A set of user services that are managed by the per-user instances of systemd; which are each an instantiation of a template service unit in the file /etc/systemd/user/dropbox@.service.

You now need to understand this:

There is one system-wide instance of systemd. It always runs. It's process #1. Only an administrator has the authority to control system services.
There are multiple per-user instances of systemd. They are started/stopped on demand as users logon/logoff. They are not process #1. There is a maximum of one per user, however many times the user is logged on. Only that user (or an administrator) has the authority to control xyr own services.

A template service unit is a way of making multiple ad-hoc service units on the fly, that differ in the template parameter. The actual instantiated service units are named as a combination of the template name and the parameter.

Combined, this all means:

In your rt@.service the parameter is a user name, used to specify the user that the service runs as and the working directory that it runs in. So you can instantiate services such as rt@euri10.service and rt@david.service. These are system services, managed by the system-wide instance of systemd, and it takes an administrator to start and stop them. It just so happens that there's one per user.
In your dropbox@.service the parameter is ignored. You can instantiate services such as dropbox@wibble.service and dropbox@phooey.service. These are user services, managed by the per-user instances of systemd. Each user has xyr own separate set of template instantiations which that user can start and stop.

You possibly didn't want your dropbox service unit to be a template. Or you're now figuring out what that Environment=DISPLAY=%i setting was all about. ☺