From owner-freebsd-current  Tue Aug  1 17:24:24 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id RAA17296
          for current-outgoing; Tue, 1 Aug 1995 17:24:24 -0700
Received: from ns1.win.net (ns1.win.net [204.215.209.3])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA17288
          for <current@freebsd.org>; Tue, 1 Aug 1995 17:24:23 -0700
Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id UAA06878 for current@freebsd.org; Tue, 1 Aug 1995 20:27:33 -0400
From: Mark Hittinger <bugs@ns1.win.net>
Message-Id: <199508020027.UAA06878@ns1.win.net>
Subject: Re: 2.2-current rlogin problem today (fwd)
To: current@freebsd.org
Date: Tue, 1 Aug 1995 20:27:32 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 932       
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.
> 
> 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.
> 
> Brian Litzinger
> brian@easynet.com
> 

Not me!  I've been bringing up a 2.2-current kernel every day for
awhile now.  Just today it started doing this.  After I rebooted
the very first rlogin attempt was rejected.  Nothing else on this
test system.  Every other one.  Weird.
Maybe they broke me trying to fix you :-)  Keep that fix away from
2.1-STABLE! :-)

Regards,

Mark Hittinger
bugs@win.net