What happens when I run systemd on a system that's already running?
up vote
-2
down vote
favorite
Out of curiosity I just ran the following on Debian 9.6:
/lib/systemd/systemd
which resulted in the following output:
Startup finished in 31ms.
with the process waiting. I killed it with Ctrl+C:
^CReceived SIGINT.
When I ran the command a second time, the output changed:
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Startup finished in 29ms.
Now I have the following 2 processes running:
1410 /lib/systemd/systemd --user
11647 /lib/systemd/systemd --user
in addition to:
1 /sbin/init
What is going on? Why did the second run result in an error while the first one didn't? Am I running three systems concurrently?
debian systemd
asked Nov 19 at 2:52
Andrey Portnoy
1003
add a comment |
up vote
-2
down vote
favorite
Out of curiosity I just ran the following on Debian 9.6:
/lib/systemd/systemd
which resulted in the following output:
Startup finished in 31ms.
with the process waiting. I killed it with Ctrl+C:
^CReceived SIGINT.
When I ran the command a second time, the output changed:
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Startup finished in 29ms.
Now I have the following 2 processes running:
1410 /lib/systemd/systemd --user
11647 /lib/systemd/systemd --user
in addition to:
1 /sbin/init
What is going on? Why did the second run result in an error while the first one didn't? Am I running three systems concurrently?
debian systemd
asked Nov 19 at 2:52
Andrey Portnoy
1003
1
I haven't read the systemd docs in depth but do recall it can actually be used by a non-root non-PID-1 account to supervise other processes.
– LawrenceC
Nov 19 at 3:03
add a comment |
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
Out of curiosity I just ran the following on Debian 9.6:
/lib/systemd/systemd
which resulted in the following output:
Startup finished in 31ms.
with the process waiting. I killed it with Ctrl+C:
^CReceived SIGINT.
When I ran the command a second time, the output changed:
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Startup finished in 29ms.
Now I have the following 2 processes running:
1410 /lib/systemd/systemd --user
11647 /lib/systemd/systemd --user
in addition to:
1 /sbin/init
What is going on? Why did the second run result in an error while the first one didn't? Am I running three systems concurrently?
debian systemd
asked Nov 19 at 2:52
Andrey Portnoy
1003
Out of curiosity I just ran the following on Debian 9.6:
/lib/systemd/systemd
which resulted in the following output:
Startup finished in 31ms.
with the process waiting. I killed it with Ctrl+C:
^CReceived SIGINT.
When I ran the command a second time, the output changed:
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Failed to connect to API bus: Connection refused
Startup finished in 29ms.
Now I have the following 2 processes running:
1410 /lib/systemd/systemd --user
11647 /lib/systemd/systemd --user
in addition to:
1 /sbin/init
What is going on? Why did the second run result in an error while the first one didn't? Am I running three systems concurrently?
debian systemd
debian systemd
asked Nov 19 at 2:52
Andrey Portnoy
1003
asked Nov 19 at 2:52
Andrey Portnoy
1003
asked Nov 19 at 2:52
Andrey Portnoy
1003
asked Nov 19 at 2:52
Andrey Portnoy
1003
asked Nov 19 at 2:52
Andrey Portnoy
1003
1003
1
I haven't read the systemd docs in depth but do recall it can actually be used by a non-root non-PID-1 account to supervise other processes.
– LawrenceC
Nov 19 at 3:03
add a comment |
1
I haven't read the systemd docs in depth but do recall it can actually be used by a non-root non-PID-1 account to supervise other processes.
– LawrenceC
Nov 19 at 3:03
1
1
I haven't read the systemd docs in depth but do recall it can actually be used by a non-root non-PID-1 account to supervise other processes.
– LawrenceC
Nov 19 at 3:03
I haven't read the systemd docs in depth but do recall it can actually be used by a non-root non-PID-1 account to supervise other processes.
– LawrenceC
Nov 19 at 3:03
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
draft saved
draft discarded
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%2fsuperuser.com%2fquestions%2f1376583%2fwhat-happens-when-i-run-systemd-on-a-system-thats-already-running%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
1
I haven't read the systemd docs in depth but do recall it can actually be used by a non-root non-PID-1 account to supervise other processes.
– LawrenceC
Nov 19 at 3:03