Alain, I understand your frustration. This is actually I think a little more serious than Low, as existence of a workaround only barely mitigates the impact of this.
The problem, I think, is that we're using expect fork, and I'm not sure why, when sshd has -D, and its clearly not reliable for this instance, since the daemon regularly forks and exits. Raising importance to High, as the reload command *must* be reliable for sshd, as failure of sshd could result in the system being totally unmanageable. ** Changed in: openssh (Ubuntu) Importance: Low => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
