Hi again,
i tried it out:
i do have a defunct child:
pid ppid
23353 1499 /usr/local/sbin/sshd
ps -ef|grep 23353
root 23354 23353 0 0:00 <defunct>
kill -l
1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL
5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE
9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS
13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGUSR1
17) SIGUSR2 18) SIGCHLD 19) SIGPWR 20) SIGWINCH
21) SIGURG 22) SIGIO 23) SIGSTOP 24) SIGTSTP
25) SIGCONT 26) SIGTTIN 27) SIGTTOU 28) SIGVTALRM
29) SIGPROF 30) SIGXCPU 31) SIGXFSZ 32) SIGWAITING
33) SIGLWP 34) SIGFREEZE 35) SIGTHAW 36) SIGCANCEL
shows 18 for SIGCHLD.
but kill -SIGCHLD 23354 or kill -18 23354 does not kill the defunct
process. My script still hangs after the kill.
Any ideas?
Martin
// Martin Decker, Systems Engineer, Data Center Operations //
// AOL Germany, Dingolfinger-Str. 2-4, D-81673 Munich, Germany //
// AIM: mdecker77 mail: mdecker77 at aol.com ICQ: 15620821 //
// Phone:+49.8966572214 //
On Fri, 8 Feb 2002, Nicolas Williams wrote:
> On Fri, Feb 08, 2002 at 05:10:57PM +0100, Martin Decker wrote:
> > hi nico,
> >
> > thanks for your ultra-quick reply! ;-)
>
> Was that it?
>
> > is this bug also related to hangs of remote ssh commands, e.g.:
> >
> > ${SSH} -v ${TARGET} "${CHOWN} -R services:services ${out_dir}
</dev/null
> > >/dev/null 2>&1" >> ${LOGFILE} 2>&1
> >
> > Or is the sigchld race only concerning scp commands?
>
> No, this bug affects any use of SSH where remote commands are run, and
> that includes sctp and sftp and interactive ssh logins and specifying a
> remote command on the ssh command line.
>
> And it affects all platforms, though some less than others as it's a
> timing issue. The fix is easy and the patch has been posted (thanks to
> Markus) and I bet the next release will include it.
>
> BTW, I'm not a member of the OpenSSH devl team...
>
> > Thanks in advance,
> >
> > Martin
>
>
> Cheers,
>
> Nico
> --
>
> Visit our website at http://www.ubswarburg.com
>
> This message contains confidential information and is intended only
> for the individual named. If you are not the named addressee you
> should not disseminate, distribute or copy this e-mail. Please
> notify the sender immediately by e-mail if you have received this
> e-mail by mistake and delete this e-mail from your system.
>
> E-mail transmission cannot be guaranteed to be secure or error-free
> as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender therefore
> does not accept liability for any errors or omissions in the contents
> of this message which arise as a result of e-mail transmission. If
> verification is required please request a hard-copy version. This
> message is provided for informational purposes and should not be
> construed as a solicitation or offer to buy or sell any securities or
> related financial instruments.
>