From owner-freebsd-hackers Thu Nov 23 05:04:28 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA06788 for hackers-outgoing; Thu, 23 Nov 1995 05:04:28 -0800 Received: from iis (iis.webnet.com.au [203.8.105.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA06782 for ; Thu, 23 Nov 1995 05:04:21 -0800 Received: from jazzy.phase-one.com.au (gw.phase-one.com.au [203.21.35.254]) by iis (8.6.12/8.6.9) with SMTP id AAA05487; Fri, 24 Nov 1995 00:08:14 +1100 Date: Thu, 23 Nov 1995 13:04:57 +1100 (EST) From: Peter Marelas X-Sender: maral@jazzy.phase-one.com.au To: Alexis Yashkov cc: freebsd-hackers@freebsd.org Subject: Re: rlogin is blocked for quite a long time In-Reply-To: <199511230525.AAA03458@harley.ios.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org Precedence: bulk On Thu, 23 Nov 1995, Alexis Yashkov wrote: > Hi, > > > > On Wed, 22 Nov 1995, J Wunsch wrote: > > > > > > > As Christoph P. Kukulies wrote: > > > > > > > > > > When I rlogin into blues.physik.rwth-aachen (-current), log out > > > > > and try to login in right again I'm getting after a minute's > > > > > pause a connection refused. > > > > > > > > I've been annoyed by this one, too. Often. Even for nearby > > > > connections (e.g. uriah.heep.sax.de <-> sax.sax.de, one hop; or even > > > > on a local ethernet). > > > > > > > > > > Im using rsh over local ether on Win95 to run xterm's. > > > > > > In .rhosts I have the hostname and the FQDN and it seems ok. > > > > > > ie. > > > gate > > > gate.co.uk > > Why should I put short names in .rhosts? I don't think this > problem has something to do with name resolution. > I believe it is a name rez problem. > > rsh is not the problem. I can do repeated rsh within short intervals. > > It's just after an explicit rlogin. Also I'm not sure if it's a client > > or server problem. Both systems are FreeBSD 2.2 resp. 2.0.5. > > I have this problem with both rsh and rlogin. Both client and server > systems are FreeBSD 2.x (I don't specify exact numbers here because > we have different releases and snaps here from 2.0.5-RELEASE till > 2.1.0-951020-SNAP and they all have the problem). I almost always > have to wait about 40-60 seconds to connect to the host again after > I've closed connection. First time I noticed this problem running > remote dump via rsh and was forced to work around (to put 60 sec. > delay between connections in the script). And one more thing, I have > no problems connecting from FreeBSD to Suns running SunOS 4.1.4 and > Solaris 2.4. If your not already doing so, run your own DNS, and see what effect it makes. Peter