From owner-freebsd-questions Sun Jul 14 21:39:44 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA23628 for questions-outgoing; Sun, 14 Jul 1996 21:39:44 -0700 (PDT) Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA23623 for ; Sun, 14 Jul 1996 21:39:42 -0700 (PDT) Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id VAA01255; Sun, 14 Jul 1996 21:37:49 -0700 From: Brian Litzinger Message-Id: <199607150437.VAA01255@MediaCity.com> Subject: Re: rsh problem, 2.1-STABLE To: bill@twwells.com (T. William Wells) Date: Sun, 14 Jul 1996 21:37:48 -0700 (PDT) Cc: freebsd-questions@freebsd.org In-Reply-To: <4s9a3k$qk8@twwells.com> from "T. William Wells" at "Jul 13, 96 07:05:24 pm" Reply-To: brian@MediaCity.com X-Mailer: ELM [version 2.4ME+ PL11 (25)] 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 T. William Wells wrote: > Note the `connection refused' after the second rsh. This occured > on both the runs of this I attempted. Yes, you read it correctly; > I am doing an rsh from admin to admin. It's a sleazy way to avoid > having to write setuid scripts. :-) It is a bug in FreeBSD that has existed since 2.0.5 and still exists in -current. when you get the 'connection refused' message or just after the 1st rsh, do a 'netstat -a' and look at the entries at the top. See that one related to rshd or rlogind that is timing out? Until that times out (30 seconds or so) you won't be able to do another of the same rsh. -- Brian Litzinger Powered by FreeBSD http[s]://www.mpress.com