** Branch linked: lp:debian/sid/openssh
--
sshd stop on two SIGHUP
https://bugs.launchpad.net/bugs/497781
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
This bug was fixed in the package openssh - 1:5.2p1-2ubuntu1
---
openssh (1:5.2p1-2ubuntu1) lucid; urgency=low
* Resynchronise with Debian. Remaining changes:
- Add support for registering ConsoleKit sessions on login.
- Drop openssh-blacklist and openssh-blacklist-extra
** Branch linked: lp:~cjwatson/openssh/debian
--
sshd stop on two SIGHUP
https://bugs.launchpad.net/bugs/497781
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
Thanks. Although I haven't managed to reproduce this myself, I've sent
my best guess at a patch upstream.
Note that this should become less important in Lucid, as sshd is now
supervised by Upstart which should ensure that it keeps running.
** Bug watch added: OpenSSH Portable Bugzilla #1692
Thanks for the patch, with this patch I can't reproduce the bug.
I toke the patch, applied it on fresh apt-get source. builded it with a
pbuilder, installed the result. With that I was unable to reproduce the problem.
Got back to karmic release of openssh and I can reproduce the bug.
So the
Forget to tell the version affected:
This was tester on jaunty (with the killall -s SIGHUP).
The server is on hardy.
So hardy and jaunty are affected.
--
sshd stop on two SIGHUP
https://bugs.launchpad.net/bugs/497781
You received this bug notification because you are a member of Ubuntu
Server
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
** Changed in: openssh (Ubuntu)
