[2579] in Athena Bugs
[David Krikorian: telnet (VS6.3A)]
daemon@ATHENA.MIT.EDU (probe@ATHENA.MIT.EDU)
Mon Jul 17 13:23:55 1989
From: <probe@ATHENA.MIT.EDU>
Date: Mon, 17 Jul 89 13:23:41 -0400
To: bugs@ATHENA.MIT.EDU
Reply-To: Richard Basch <probe@ATHENA.MIT.EDU>
Sounds like a process-group problem to me...
-Richard
------- Forwarded Message
Date: Mon, 17 Jul 89 12:03:47 -0400
From: David Krikorian <dkk@ATHENA.MIT.EDU>
To: bugs@ATHENA.MIT.EDU
Subject: telnet (VS6.3A)
Reply-To: dkk@ATHENA.MIT.EDU
Home: 47 Lake St., Arlington, MA 02174, (617) 646-9289
Office: MIT Bldg. E40-358A, (617) 253-8651, 258-8736 (fax)
When telnet is interrupted with "kill" from another shell, the telnet
not only exits, but it takes the parent csh with it, no matter what
precautions I take.
1. Get an xterm, with a csh running in it. (Preferably, this should
be your login xterm, so telnet can log you out abruptly and
violently...)
2. Type "set ignoreeof", just to put up a token struggle.
3. Type "telnet randomhostname", then ignore that window.
4. In another window, find the pid of the telnet, and "kill" it, or
even try to "kill -STOP" it. Telnet doesn't care, it happily blows
away the shell no matter where you tell it to go.
5. Watch the xterm with the telnet, and see it display something like:
athena%
Use "exit" to leave csh.
athena%
Use "exit" to leave csh.
and so on about 10 times before the xterm goes poof.
6. Go have a drink.
7. Return to your office and login again.
------- End Forwarded Message
