I used to just have to add-wants ssh.service to rescue.target and I could isolate to rescue mode for remote system maintainence without loosing remote access to the server. After an upgrade, even though ssh.service is wanted by rescue.target, it is still killed if I isolate. How can I figure out why? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
- [systemd-devel] ssh.service in rescue.target Phillip Susi
- Re: [systemd-devel] ssh.service in rescue.target Lennart Poettering
- Re: [systemd-devel] ssh.service in rescue.targ... Phillip Susi
- Re: [systemd-devel] ssh.service in rescue.... Lennart Poettering
- Re: [systemd-devel] ssh.service in res... Phillip Susi
- Re: [systemd-devel] ssh.service i... Mantas Mikulėnas
- Re: [systemd-devel] ssh.service i... Lennart Poettering
- Re: [systemd-devel] ssh.servi... Phillip Susi
- Re: [systemd-devel] ssh.s... Michael Biebl
- Re: [systemd-devel] ssh.s... Phillip Susi
- Re: [systemd-devel] ssh.s... Simon McVittie