https://bugzilla.mindrot.org/show_bug.cgi?id=2993
Darren Tucker <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Darren Tucker <[email protected]> --- As a general rule, if a userspace program like sshd can cause a kernel panic that indicates a problem with the kernel. Anyway, I do have a proposed experiment for you: run the stock sshd *and* your new sshd on a different port (eg /usr/local/sbin/sshd -d -p 222) then reboot and see if it panics. I'm wondering if systemd is somehow getting out of sync and waiting for sshd to stop even though it already has and the kernel eventually shoots pid 1. BTW: > ("/usr/local/sbin/sshd -4 -f /etc/ssh/sshd_config &") The & is not needed, sshd will daemonize itself after startup. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
