Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!daffy!uwvax!uchinews!ncar!newsfeed.internetmci.com!EU.net!Germany.EU.net!news.dfn.de!news.uni-augsburg.de!lrz-muenchen.de!fauern!news.tu-chemnitz.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Rlogin on connection drop
Date: 10 Aug 1995 14:56:42 +0200
Organization: Private U**x site, Dresden.
Lines: 25
Message-ID: <40cvma$4cu@bonnie.tcd-dresden.de>
References: <40anm2$ms4@news.bu.edu>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Mikhail Teterin <mi@cs.bu.edu> wrote:
>If connection drops during rlogin session, rlogin remains occupying the
>virtual terminal. If killed from another terminal -- dies (-:, but csh does
>not respond after that -- has to be killed as well. Where to go to fix this?
Dropping a SLIP or PPP transport underlying some IP service is very
much the same like pulling the Ethernet cable for a while: you won't
*expect* the TCP connection to break (for a certain time). Instead,
you are able to re-establish the transport protocol (most likely by
redialing), and can continue the suspended TCP channel.
Quit your rlogin session as usual with ~.
Killing it... did'ya kill it with ``kill -9''? You moron get what you
deserve. -9 (aka -KILL) is last-resort only! *ALWAYS* try -1 (aka
-HUP) or -15 (aka -TERM) first. This will give rlogin a chance to
clean up. (I'm quite sure your csh still did respond, but your kill
-9 left the terminal in -echo -icrnl state, so you didn't see any
character echos, nor did ^M act as a line feed. You explicitly had to
type ^J in order to terminate an input line.)
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)