From owner-freebsd-current  Tue Aug  1 17:17:48 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id RAA16801
          for current-outgoing; Tue, 1 Aug 1995 17:17:48 -0700
Received: from easynet.com (easy1.easynet.com [199.2.26.10])
          by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id RAA16795
          for <current@freebsd.org>; Tue, 1 Aug 1995 17:17:47 -0700
Received: by easynet.com (Smail3.1.28.1 #7)
	id m0sdRVQ-000rfUC; Tue, 1 Aug 95 17:17 WET DST
Message-Id: <m0sdRVQ-000rfUC@easynet.com>
From: brian@MediaCity.com (Brian Litzinger)
Subject: Re: 2.2-current rlogin problem today
To: bugs@ns1.win.net (Mark Hittinger)
Date: Tue, 1 Aug 1995 17:17:52 -0700 (PDT)
Cc: current@freebsd.org
In-Reply-To: <199508012343.TAA11428@ns1.win.net> from "Mark Hittinger" at Aug 1, 95 07:43:36 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1031      
Sender: current-owner@freebsd.org
Precedence: bulk


> Just noticed something about today's (1-aug) 2.2 tcp/ip.  Every other
> rlogin is rejected.  Every other rlogin is accepted.  I get a connection
> closed error exactly every other time heh.

> Also Xwindows can only be started once, it exits after startup after that.
> Reboot clears this up.

hah! That is two other people experiencing the same problem I am. Yeah!
The problem has been around for awhile.  

In my experience it isn't actually every other.  It is a timeout
thing. 

Do your rsh/rlogin thing and get to the stage where you are about to
do a rsh/rlogin you know is going to fail/timeout.

Do a netstat -a on the destination machine, and you'll see near the beginning
of the list one or two connections related to the rlogin/rsh you just
exited.  They/it will be in close/wait or some finish state.

You will not be able to rsh/rlogin in again until those entries
have finished up/timed out.  If you wait for them to disappear before
your next rsh/rlogin the attempt won't fail.

Brian Litzinger
brian@easynet.com