From owner-freebsd-questions  Mon Jun 17 16:08:24 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA07819
          for questions-outgoing; Mon, 17 Jun 1996 16:08:24 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA07803
          for <questions@freebsd.org>; Mon, 17 Jun 1996 16:08:13 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA08975; Mon, 17 Jun 1996 16:06:06 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199606172306.QAA08975@phaeton.artisoft.com>
Subject: Re: Rlogin delay
To: brian@MediaCity.com
Date: Mon, 17 Jun 1996 16:06:06 -0700 (MST)
Cc: terry@lambert.org, questions@freebsd.org
In-Reply-To: <199606172243.PAA21939@MediaCity.com> from "Brian Litzinger" at Jun 17, 96 03:43:51 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > I've observed something concerning rlogin that is a bit odd to me, and 
> > > increasingly annoying for my users. When a user logs off and then tries 
> > > to re-log within a reasonable delay from another machine on the local 
> > > network, the login will be ingored for a very long time (10-60 seconds 
> > > seems typical). I checked the /etc/inetd.conf to make sure it was okay:
> 
> I've observed the following behavior between two FreeBSD of every
> version since 2.0.5
> 
> freebsd1# rsh freebsd2 ls -a
> ./              .cshrc          .klogin         .rhosts
> ../             .fvwmrc         .login          .xsession
> .Xdefaults      .history        .profile                    
> 
> freebsd1# rsh freebsd2 ls -a
> (30 or so seconds later)
> Connection refused

Interesting.

Did you know that FreeBSD and Linux handle route errors differently,
and that maybe a timeout on disconnect is being misinterpreted?

Linux drops the connection (making it somewhat succeptible to the
"NT sniper bug", actually), and FreeBSD retries.

Matt Day posted something about this to -hackers or to -current
a while ago.

If you are stuck in an incremental back-off, it could explain a few
things.

It would also explain why the change came in at the same time as the
4.4 Lite code came in in place of the 4.3 (Net/2) code.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.