*BSD News Article 48400


Return to BSD News archive

Path: sserve!euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!lll-winken.llnl.gov!fnnews.fnal.gov!gw1.att.com!news.bu.edu!csb!mi
From: mi@csb.bu.edu (Mikhail Teterin)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Rlogin on connection drop
Date: 11 Aug 1995 02:29:28 GMT
Organization: Computer Science Department, Boston University, Boston, MA, USA
Lines: 29
Message-ID: <40efa8$ldt@news.bu.edu>
References: <40anm2$ms4@news.bu.edu> <40cvma$4cu@bonnie.tcd-dresden.de>
NNTP-Posting-Host: csb.bu.edu

Some time ago (10 Aug 1995 14:56:42 +0200) honorable J Wunsch, 
residing at j@bonnie.heep.sax.de wrote:

|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

Before calling me a moron, wait for an answer (or did I show
this characteristic of mine before?). rlogin leaves with a default
`kill' or with `kill -1', but leaves csh in the unusable state --
gives a prompt, that's it. csh can be killed with -1 or -9, that
does not show any obvious difference -- getty comes up.

My redial whill give a new IP-address, so rlogin will not catch up
(actually, I tried, already). Thanks anyway,

	-mi
-- 
И пусть никто не уйдёт обиженным...
		-- Why is that 2 o'clock all the time?!
		-- It is a manometer!!!