From owner-freebsd-questions  Tue Jun 18 06:41:13 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA26648
          for questions-outgoing; Tue, 18 Jun 1996 06:41:13 -0700 (PDT)
Received: from rk.ios.com (rk.ios.com [198.4.75.55])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA26643
          for <questions@FreeBSD.ORG>; Tue, 18 Jun 1996 06:41:11 -0700 (PDT)
Received: (from rashid@localhost) by rk.ios.com (8.6.11/8.6.9) id JAA13296; Tue, 18 Jun 1996 09:39:01 -0400
From: Rashid  Karimov <rashid@rk.ios.com>
Message-Id: <199606181339.JAA13296@rk.ios.com>
Subject: Re: Rlogin delay
To: terry@lambert.org (Terry Lambert)
Date: Tue, 18 Jun 1996 09:39:01 -0400 (EDT)
Cc: dbabler@Rigel.orionsys.com, terry@lambert.org, questions@FreeBSD.ORG
In-Reply-To: <199606172302.QAA08961@phaeton.artisoft.com> from "Terry Lambert" at Jun 17, 96 04:02:45 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

		Hi there folx,

> 
> > > > 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:
> > > 
> > > Did you turn on the global SO_KEEPALIVE that everyone was talking about?
> > > People who wanted this were MUD people and similar sites, without regard
> > > for the impact on things that didn't expect it to be on.
> > > 
> > I basically installed/built whetever was the standard configuration 
> > (2.1-stable)... I also tried the -n option for rlogind in /etc/inetd.conf 
> > to no effect. The first couple of relog attempts usually work in a second 
> > or two - subsequently, the delays required get pretty long.
> 
> I was about to suggest -n in case it was a client problem with the connection
> not being terminated correctly...
> 
> Actually, I screwed up before, I meant to say SO_LINGER.  I said
> keepalive because I knew that was switchable.
> 
> If you are globally setting SO_LINGER -- don't.
> 
> 
> You may also want to check to see (via ps -gax) if the rlogind had
> exited, or it's the TCP trying to ack the client that's causing
> the hang.

	I see this behaviour for more than a year now - it's very typical.
	In my situation it's all FreeBSDs , so it's not a problem with 
	brain-dead client :) by some other vendor.


	Rashid.