[Bug 412972] Re: bad signal mask of ssh sessions

2009-12-04 Thread Colin Watson
*** This bug is a duplicate of bug 407428 *** https://bugs.launchpad.net/bugs/407428 ** This bug has been marked a duplicate of bug 407428 worker signal mask inherited by children -- bad signal mask of ssh sessions https://bugs.launchpad.net/bugs/412972 You received this bug notification

[Bug 412972] Re: bad signal mask of ssh sessions

2009-12-04 Thread Colin Watson
*** This bug is a duplicate of bug 407428 *** https://bugs.launchpad.net/bugs/407428 ** This bug has been marked a duplicate of bug 407428 worker signal mask inherited by children -- bad signal mask of ssh sessions https://bugs.launchpad.net/bugs/412972 You received this bug notification

[Bug 412972] Re: bad signal mask of ssh sessions

2009-10-05 Thread Ken Bloom
This looks related to http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=549376, as I (the original reporter of that bug) am seeing the same SigBlk mask on my root sshd process. It may also be related to https://bugzilla.mindrot.org/show_bug.cgi?id=271 where sshd was inheriting a bad signal mask

[Bug 412972] Re: bad signal mask of ssh sessions

2009-10-05 Thread Ken Bloom
I'm running Debian Unstable booting with file-rc, and there are several system daemons that have screwy SigBlk masks, of which sshd is one. They are listed in the attached commands file. You can get the data for a similar report on your own machine by running the following commands (as root):

[Bug 412972] Re: bad signal mask of ssh sessions

2009-10-05 Thread Ken Bloom
Bingo. The bug is at https://bugs.launchpad.net/ubuntu/+source/udev/+bug/407428 and it's already been fixed in udev. -- bad signal mask of ssh sessions https://bugs.launchpad.net/bugs/412972 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to

[Bug 412972] Re: bad signal mask of ssh sessions

2009-10-05 Thread Ken Bloom
This looks related to http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=549376, as I (the original reporter of that bug) am seeing the same SigBlk mask on my root sshd process. It may also be related to https://bugzilla.mindrot.org/show_bug.cgi?id=271 where sshd was inheriting a bad signal mask

[Bug 412972] Re: bad signal mask of ssh sessions

2009-10-05 Thread Ken Bloom
I'm running Debian Unstable booting with file-rc, and there are several system daemons that have screwy SigBlk masks, of which sshd is one. They are listed in the attached commands file. You can get the data for a similar report on your own machine by running the following commands (as root):

[Bug 412972] Re: bad signal mask of ssh sessions

2009-10-05 Thread Ken Bloom
Bingo. The bug is at https://bugs.launchpad.net/ubuntu/+source/udev/+bug/407428 and it's already been fixed in udev. -- bad signal mask of ssh sessions https://bugs.launchpad.net/bugs/412972 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 412972] Re: bad signal mask of ssh sessions

2009-09-02 Thread Scott James Remnant
Thanks, this confirms what we expected. The TERM signal is being delivered to the process, it's just that the process's mask is set to block that signal and it's still pending. We're not entirely sure yet what causes this bug; it's certainly not a procps or kernel bug, so I'm reassigning to

[Bug 412972] Re: bad signal mask of ssh sessions

2009-09-02 Thread Scott James Remnant
Thanks, this confirms what we expected. The TERM signal is being delivered to the process, it's just that the process's mask is set to block that signal and it's still pending. We're not entirely sure yet what causes this bug; it's certainly not a procps or kernel bug, so I'm reassigning to

[Bug 412972] Re: bad signal mask of ssh sessions

2009-09-01 Thread Michael Helmling
Here you go ... # cat /proc/12218/status Name: sleep State: S (sleeping) Tgid: 12218 Pid:12218 PPid: 12202 TracerPid: 0 Uid:0 0 0 0

[Bug 412972] Re: bad signal mask of ssh sessions

2009-08-27 Thread Scott James Remnant
Michael: could you also give us the /proc/PID/status of a sleep after you've sent it the TERM signal ** Summary changed: - can only kill processes with -9 in karmic from SSH sessions, -TERM does not work + bad signal mask of ssh sessions -- bad signal mask of ssh sessions