bugzilla-daemon at mindrot.org
2002-Jul-12 15:22 UTC
[Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup
http://bugzilla.mindrot.org/show_bug.cgi?id=273 ------- Additional Comments From sam at neutrino.phy.uct.ac.za 2002-07-13 01:22 ------- i also have this exact same problem using OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f i start a program with "nohup <program> &" and upon returning to my native machine, the terminal is balnk, frozen with no bash prompt. i must kill the ssh pid form another terminal to get my original terminal back. thanks, Sam ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Jul-12 16:35 UTC
[Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup
http://bugzilla.mindrot.org/show_bug.cgi?id=273 ------- Additional Comments From jmknoble at pobox.com 2002-07-13 02:35 -------> i start a program with "nohup <program> &" and > upon returning to my native machine, the terminal > is balnk, frozen with no bash prompt.Don't do that. Do this instead: (nohup <program> &) Note the order of the '&' and the enclosing parentheses. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Jul-12 18:04 UTC
[Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup
http://bugzilla.mindrot.org/show_bug.cgi?id=273 ------- Additional Comments From kerry.schwab at wnco.com 2002-07-13 04:04 ------- (nohup ./script &) is a workaround of sorts, but that's not really a good answer. People expect ssh to be an rsh replacement, and rsh doesn't require a double fork to avoid the hang-on-exit. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
Nicolas.Williams at ubsw.com
2002-Jul-12 18:25 UTC
[Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup
> People expect ssh to be an rsh replacement, > and rsh doesn't require a double fork > to avoid the hang-on-exit.This thing comes up over and over again. And the same back-and-forth arguments take place. SSH is more than a secure RSH. It truly is. You can't have it be two conflicting things at the same time. Read the archives. I believe people can learn. I really do. [NOTE: I'm not an OpenSSH developer nor do I speak for them.] 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.
Reasonably Related Threads
- [Bug 273] New: sshd hangs on shell exit if user spawned child with /bin/nohup
- [Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup
- [Bug 273] sshd hangs on shell exit if user spawned child with/bin/nohup
- [Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup
- [Bug 1463] New: Running nohup sleep 70 & and then exiting shell, hangs ssh