From owner-freebsd-questions Fri Jun 14 12:29:46 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09872 for questions-outgoing; Fri, 14 Jun 1996 12:29:46 -0700 (PDT) Received: from Rigel.orionsys.com (root@rigel.orionsys.com [205.148.224.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA09865 for ; Fri, 14 Jun 1996 12:29:43 -0700 (PDT) Received: (from dbabler@localhost) by Rigel.orionsys.com (8.7.5/8.6.9) id MAA08564; Fri, 14 Jun 1996 12:29:41 -0700 (PDT) Date: Fri, 14 Jun 1996 12:29:40 -0700 (PDT) From: Dave Babler To: questions@FreeBSD.org Subject: Rlogin delay Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: ---- /etc/inet.conf #login stream tcp nowait root /usr/libexec/rlogind rlogind login stream tcp nowait root /usr/local/libexec/tcpd rlogind ---- I've recently added the tc_wrappers port, hence the tcpd entry (it works great, BTW). Contrary to the setup, it seems to behaving as though it had been setup as 'wait' instead of 'nowait'. As a test, I logged in from the other machine and then logged off and periodically ran netstat. This is what I see: ---- 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 localhost.hermes localhost.domain TIME_WAIT tcp 0 0 rigel.login orionsys.com.1022 TIME_WAIT tcp 0 0 rigel.1235 204.162.115.56.rwhois FIN_WAIT_2 ---- logged off several seconds ago ---- tcp 0 0 localhost.1249 localhost.domain TIME_WAIT tcp 0 0 rigel.login orionsys.com.1022 TIME_WAIT tcp 0 0 rigel.1235 204.162.115.56.rwhois FIN_WAIT_2 ---- logoff +10 seconds ---- tcp 0 0 localhost.1250 localhost.domain TIME_WAIT tcp 0 0 rigel.login orionsys.com.1022 TIME_WAIT ---- logoff +30 seconds ---- tcp 0 0 localhost.1253 localhost.domain TIME_WAIT tcp 0 0 localhost.1252 localhost.domain TIME_WAIT tcp 0 0 rigel.login orionsys.com.1022 TIME_WAIT ---- logoff +45 seconds ---- tcp 0 0 localhost.1256 localhost.domain TIME_WAIT tcp 0 0 localhost.1255 localhost.domain TIME_WAIT tcp 0 0 rigel.login orionsys.com.1022 TIME_WAIT ---- finally gone! over 60 seconds later ---- udp 0 0 localhost.domain *.* udp 0 0 rigel.domain *.* This is somewhat trimmed down.. it was running with 2 other users using TinTin. I don't know if it has any relevance to the re-log problem, but I've also had users report significant delays (approaching 60 *seconds*) on their connections to the MUD server (Mortal Realms) using TinTin and I've been putting that down to overloaded MCI routers in the SF bay area. Thanks! -Dave Babler