Why is there a `systemd` process owned by each user that is logged in?
Clash Royale CLAN TAG#URR8PPP
In my ps output:
root 1 0.0 0.0 225552 5316 ? Ss /lib/systemd/systemd --system --deserialize 19
message+ 572 0.0 0.0 51564 3076 ? Ss /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root 590 0.0 0.0 71084 2084 ? Ss /lib/systemd/systemd-logind
t 929 0.0 0.0 76872 1988 ? Ss /lib/systemd/systemd --user
t 980 0.0 0.0 50792 2688 ? Ss /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
systemd+ 2632 0.0 0.0 71240 2464 ? Ss /lib/systemd/systemd-resolved
systemd+ 2637 0.0 0.0 143976 712 ? Ssl /lib/systemd/systemd-timesyncd
root 2642 0.0 0.4 232544 37308 ? S<s /lib/systemd/systemd-journald
root 3334 0.0 0.0 46108 2252 ? Ss /lib/systemd/systemd-udevd
testme 22693 0.0 0.0 76964 3428 ? Ss /lib/systemd/systemd --user
Why do I have so many systemd related processes?
In particular, why is there a systemd process owned by each user that is logged in?
In the boot sequence of Linux, the kernel starts the init system as the first process, and then the init process runs login so that each user can login. I think the init system should be run as as a singleton process, regardless of how many users login, and regardless of whether the init system is sysvinit or systemd, correct?
Does root have to log in to start its systemd process?
For those systemd processes not owned by root, are they run as daemons?
Thanks.
systemd init sysvinit
asked Dec 19 at 13:06
Tim
26k74246455
add a comment |
In my ps output:
root 1 0.0 0.0 225552 5316 ? Ss /lib/systemd/systemd --system --deserialize 19
message+ 572 0.0 0.0 51564 3076 ? Ss /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root 590 0.0 0.0 71084 2084 ? Ss /lib/systemd/systemd-logind
t 929 0.0 0.0 76872 1988 ? Ss /lib/systemd/systemd --user
t 980 0.0 0.0 50792 2688 ? Ss /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
systemd+ 2632 0.0 0.0 71240 2464 ? Ss /lib/systemd/systemd-resolved
systemd+ 2637 0.0 0.0 143976 712 ? Ssl /lib/systemd/systemd-timesyncd
root 2642 0.0 0.4 232544 37308 ? S<s /lib/systemd/systemd-journald
root 3334 0.0 0.0 46108 2252 ? Ss /lib/systemd/systemd-udevd
testme 22693 0.0 0.0 76964 3428 ? Ss /lib/systemd/systemd --user
Why do I have so many systemd related processes?
In particular, why is there a systemd process owned by each user that is logged in?
In the boot sequence of Linux, the kernel starts the init system as the first process, and then the init process runs login so that each user can login. I think the init system should be run as as a singleton process, regardless of how many users login, and regardless of whether the init system is sysvinit or systemd, correct?
Does root have to log in to start its systemd process?
For those systemd processes not owned by root, are they run as daemons?
Thanks.
systemd init sysvinit
asked Dec 19 at 13:06
Tim
26k74246455
add a comment |
In my ps output:
root 1 0.0 0.0 225552 5316 ? Ss /lib/systemd/systemd --system --deserialize 19
message+ 572 0.0 0.0 51564 3076 ? Ss /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root 590 0.0 0.0 71084 2084 ? Ss /lib/systemd/systemd-logind
t 929 0.0 0.0 76872 1988 ? Ss /lib/systemd/systemd --user
t 980 0.0 0.0 50792 2688 ? Ss /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
systemd+ 2632 0.0 0.0 71240 2464 ? Ss /lib/systemd/systemd-resolved
systemd+ 2637 0.0 0.0 143976 712 ? Ssl /lib/systemd/systemd-timesyncd
root 2642 0.0 0.4 232544 37308 ? S<s /lib/systemd/systemd-journald
root 3334 0.0 0.0 46108 2252 ? Ss /lib/systemd/systemd-udevd
testme 22693 0.0 0.0 76964 3428 ? Ss /lib/systemd/systemd --user
Why do I have so many systemd related processes?
In particular, why is there a systemd process owned by each user that is logged in?
In the boot sequence of Linux, the kernel starts the init system as the first process, and then the init process runs login so that each user can login. I think the init system should be run as as a singleton process, regardless of how many users login, and regardless of whether the init system is sysvinit or systemd, correct?
Does root have to log in to start its systemd process?
For those systemd processes not owned by root, are they run as daemons?
Thanks.
systemd init sysvinit
asked Dec 19 at 13:06
Tim
26k74246455
In my ps output:
root 1 0.0 0.0 225552 5316 ? Ss /lib/systemd/systemd --system --deserialize 19
message+ 572 0.0 0.0 51564 3076 ? Ss /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root 590 0.0 0.0 71084 2084 ? Ss /lib/systemd/systemd-logind
t 929 0.0 0.0 76872 1988 ? Ss /lib/systemd/systemd --user
t 980 0.0 0.0 50792 2688 ? Ss /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
systemd+ 2632 0.0 0.0 71240 2464 ? Ss /lib/systemd/systemd-resolved
systemd+ 2637 0.0 0.0 143976 712 ? Ssl /lib/systemd/systemd-timesyncd
root 2642 0.0 0.4 232544 37308 ? S<s /lib/systemd/systemd-journald
root 3334 0.0 0.0 46108 2252 ? Ss /lib/systemd/systemd-udevd
testme 22693 0.0 0.0 76964 3428 ? Ss /lib/systemd/systemd --user
Why do I have so many systemd related processes?
In particular, why is there a systemd process owned by each user that is logged in?
In the boot sequence of Linux, the kernel starts the init system as the first process, and then the init process runs login so that each user can login. I think the init system should be run as as a singleton process, regardless of how many users login, and regardless of whether the init system is sysvinit or systemd, correct?
Does root have to log in to start its systemd process?
For those systemd processes not owned by root, are they run as daemons?
Thanks.
systemd init sysvinit
systemd init sysvinit
asked Dec 19 at 13:06
Tim
26k74246455
asked Dec 19 at 13:06
Tim
26k74246455
edited Dec 19 at 13:16
asked Dec 19 at 13:06
Tim
26k74246455
asked Dec 19 at 13:06
Tim
26k74246455
asked Dec 19 at 13:06
Tim
26k74246455
26k74246455
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The init process is pid 1, and root most certainly doesn’t have to log in to start it. The other processes aren’t the init process.
The various per-user systemd processes manage each user’s services. These include user services (systemctl --user start ...), and a number of “per-user dæmons” (in GNOME, you’ll see PulseAudio, various GVFS processes, etc.).
The other systemd processes handle specific services: the resolver, the time synchronisation service, the journal, etc.
Your ps output shows that none of these processes has a controlling terminal, so they’re all running as dæmons (for some value of dæmon).
systemd has very good documentation, try man systemd, man systemd-logind etc.
answered Dec 19 at 13:14
Stephen Kitt
164k24365444
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489907%2fwhy-is-there-a-systemd-process-owned-by-each-user-that-is-logged-in%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The init process is pid 1, and root most certainly doesn’t have to log in to start it. The other processes aren’t the init process.
The various per-user systemd processes manage each user’s services. These include user services (systemctl --user start ...), and a number of “per-user dæmons” (in GNOME, you’ll see PulseAudio, various GVFS processes, etc.).
The other systemd processes handle specific services: the resolver, the time synchronisation service, the journal, etc.
Your ps output shows that none of these processes has a controlling terminal, so they’re all running as dæmons (for some value of dæmon).
systemd has very good documentation, try man systemd, man systemd-logind etc.
answered Dec 19 at 13:14
Stephen Kitt
164k24365444
add a comment |
The init process is pid 1, and root most certainly doesn’t have to log in to start it. The other processes aren’t the init process.
The various per-user systemd processes manage each user’s services. These include user services (systemctl --user start ...), and a number of “per-user dæmons” (in GNOME, you’ll see PulseAudio, various GVFS processes, etc.).
The other systemd processes handle specific services: the resolver, the time synchronisation service, the journal, etc.
Your ps output shows that none of these processes has a controlling terminal, so they’re all running as dæmons (for some value of dæmon).
systemd has very good documentation, try man systemd, man systemd-logind etc.
answered Dec 19 at 13:14
Stephen Kitt
164k24365444
add a comment |
The init process is pid 1, and root most certainly doesn’t have to log in to start it. The other processes aren’t the init process.
The various per-user systemd processes manage each user’s services. These include user services (systemctl --user start ...), and a number of “per-user dæmons” (in GNOME, you’ll see PulseAudio, various GVFS processes, etc.).
The other systemd processes handle specific services: the resolver, the time synchronisation service, the journal, etc.
Your ps output shows that none of these processes has a controlling terminal, so they’re all running as dæmons (for some value of dæmon).
systemd has very good documentation, try man systemd, man systemd-logind etc.
answered Dec 19 at 13:14
Stephen Kitt
164k24365444
The init process is pid 1, and root most certainly doesn’t have to log in to start it. The other processes aren’t the init process.
The various per-user systemd processes manage each user’s services. These include user services (systemctl --user start ...), and a number of “per-user dæmons” (in GNOME, you’ll see PulseAudio, various GVFS processes, etc.).
The other systemd processes handle specific services: the resolver, the time synchronisation service, the journal, etc.
Your ps output shows that none of these processes has a controlling terminal, so they’re all running as dæmons (for some value of dæmon).
systemd has very good documentation, try man systemd, man systemd-logind etc.
answered Dec 19 at 13:14
Stephen Kitt
164k24365444
edited Dec 19 at 13:19
answered Dec 19 at 13:14
Stephen Kitt
164k24365444
answered Dec 19 at 13:14
Stephen Kitt
164k24365444
answered Dec 19 at 13:14
Stephen Kitt
164k24365444
164k24365444
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489907%2fwhy-is-there-a-systemd-process-owned-by-each-user-that-is-logged-in%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown