[Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup

[bugzilla-daemon at mindrot.org]

http://bugzilla.mindrot.org/show_bug.cgi?id=273





------- Additional Comments From kerry.schwab at wnco.com  2002-06-12 06:26 -------
Debug output, with comments:
Get this once i'm in:
>>[some omitted for brevity]
>>debug1: session_new: session 0
>>debug1: Allocating pty.
>>debug1: session_pty_req: session 0 alloc /dev/pts/12
>>debug1: fd 4 setting TCP_NODELAY
>>debug1: Entering interactive session.
>>debug1: fd 7 setting O_NONBLOCK
>>debug1: fd 10 setting O_NONBLOCK
>>debug1: fd 11 setting O_NONBLOCK
>>debug1: server_init_dispatch_13
>>debug1: server_init_dispatch_15
Now I start the "nohup job" with ./nohup somescript &
I then try to exit the ksh shell.
Ksh first tells you "You have running jobs" ( normal...)
then I give the second exit.
At that point, my ksh becomes a <defunct> process (zombie).
sshd apparently gets the SIGCHLD:
>debug1: Received SIGCHLD.
But, my ssh session is "hung".

sshd itself is running poll() over and over on fd0,1,2.

If I then kill the nohupped process ( from another session ), the session
is closed:

>>debug1: End of interactive session; stdin 20, stdout (read 584, sent 584), 
>>stderr 0 bytes.
>>debug1: Command exited with status 0.
>>debug1: Received exit confirmation.
>>debug1: session_close: session 0 pid 24164
>>debug1: session_pty_cleanup: session 0 release /dev/pts/12

Please let me know if you need more detail.
I'll be happy to help any way I can.







------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.