Finally, I find this describe the common problem
In my first trying to install karmic via network install script and update to
the latest version. I found my desktop refuse to interrupt process with Ctrl +
c in ssh. It's really hard to use because I only work with sshI was
thinking that
Well. Provide a piece of code as a workaround. compile the following C code:
#include "signal.h"
int main( int argc, char ** argv )
{
sigset_t oldset, newset;
sigfillset( &newset );
sigprocmask( SIG_UNBLOCK, &newset, &oldset );
int pid = fo
Hi Brett.
I forgot to mention that:
You need to logout from current console. Then login your machine.
Sorry for that.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Hi Michael
Please paste the result of "cat /proc/`pidof sshd | awk '{print
$1}'`/status | grep SigBlk". If the problem is not caused by sigmask.
The workaround can't work. :)
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received t
Don't know the developer already get the root cause or not. I can
provide some clue deeper into this issue.
When Karmic starts the ssh and other several services(udevd,dhcp etc.), it uses
a wrong Sigmask set for the program:
Check the Sigblk for sshd:
$ cat /proc/`pidof sshd| awk '{print $1}'`/st
Seems latest update fix the problem. But now, I get ext4 and shutdown
problem.
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
