From owner-freebsd-questions Mon Jun 17 14:31:37 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00827 for questions-outgoing; Mon, 17 Jun 1996 14:31:37 -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 OAA00819 for ; Mon, 17 Jun 1996 14:31:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA08654; Mon, 17 Jun 1996 14:29:17 -0700 From: Terry Lambert Message-Id: <199606172129.OAA08654@phaeton.artisoft.com> Subject: Re: Rlogin delay To: dbabler@Rigel.orionsys.com (Dave Babler) Date: Mon, 17 Jun 1996 14:29:17 -0700 (MST) Cc: questions@FreeBSD.ORG In-Reply-To: from "Dave Babler" at Jun 14, 96 12:29:40 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: [ ... ] > ---- connection active, test is from port 1022 ---- > Active Internet connections > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp 0 0 rigel.login orionsys.com.1022 ESTABLISHED > ---- 1022 just logged off ---- > tcp 0 0 rigel.login orionsys.com.1022 TIME_WAIT > ---- finally gone! over 60 seconds later ---- 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. This would be a natural side effect of the thing having data to drain that your client didn't wait for because of the disconnect on the OOB. This is really a problem with setting SO_KEEPALIVE, not with rlogin. If you want it to operate correctly, you would need to delay the OOB disconnect for the flush interval for the non-OOB data (or add a "disconnect ack wait" to the server and a "disconnect ack" to the client. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.