Re: ssh.service in rescue.target

[Phillip Susi <phill@xxxxxxxxxxxx>]

Lennart Poettering writes:

> Look at the logs?
>
> if they are not immeidately helpful, consider turning on debug logging
> in systemd first, and then redoing the action and then looking at the
> logs. You can use "systemd-analyze log-level debug" to turn on debug
> logging in PID 1 any time.

It appears that systemd decides that ssh.service should remain running,
removes the redundant start job since it is already running, but
killprocs sends sshd a SIGTERM, so it shuts down, and systemd decides
not to restart it.  iirc, there was a list of pids that would NOT be
killed at that stage... it appears that the pid for ssh.service isn't
getting placed in that list.  How did that work again?
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel