The code looks something like this: [ option parsing, config check, etc ] sshd.c, line 1744: daemon() [ reinit logs, start random number generator, chdir to /, ignore SIGPIPE ] sshd.c, line 1774: server_listen() -- socket(), bind(), listen(), etc.
So, there's already a race between considering it started (at the fork caused by daemon()), and sshd listening, right? Its just that now we're considering it started before the config check and option parsing, so that does give any dependent upstart jobs a bigger head start than they already had. -- 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
