systemctl rescue does not kill interactive shells?
by berndbausch from LinuxQuestions.org on (#52XVH)
I thought that the rescue target, which I can enter from multi-user with the commands systemctl rescueor systemctl isolate rescue, is single-user mode.
However I just found that on my Centos 8 server, existing interactive sessions continue. Also, systemctl rescue is supposed to send a message to all logged-in users but doesn't. I also expected it to shut down networking - it is obviously up.
The sshd service is shut down.
On a Debian 10 server, the behavior is different. The main network interface is shut down, but the bash process that I launched by logging on via ssh is still running.
I expected all interactive sessions and the network interfaces to be stopped. Is there a problem with the servers' configuration or is my expectation wrong?
However I just found that on my Centos 8 server, existing interactive sessions continue. Also, systemctl rescue is supposed to send a message to all logged-in users but doesn't. I also expected it to shut down networking - it is obviously up.
The sshd service is shut down.
On a Debian 10 server, the behavior is different. The main network interface is shut down, but the bash process that I launched by logging on via ssh is still running.
I expected all interactive sessions and the network interfaces to be stopped. Is there a problem with the servers' configuration or is my expectation wrong?