From owner-freebsd-current Thu Jun 27 21:42:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05866 for current-outgoing; Thu, 27 Jun 1996 21:42:20 -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 VAA05861 for ; Thu, 27 Jun 1996 21:42:18 -0700 (PDT) Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id VAA24389; Thu, 27 Jun 1996 21:41:00 -0700 From: Brian Litzinger Message-Id: <199606280441.VAA24389@MediaCity.com> Subject: Re: Has anyone noticed a problem with rshd in -current? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 27 Jun 1996 21:40:59 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: <199606250332.UAA16404@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 24, 96 08:32:23 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > It seems like 1 out of every 3 attempts from another host, it > exits immediately and a "Connection refused" is generated on the > client. > > Just checking to see if it's me and my personal weirdness field, first. :) > > Jordan Many people have noticed it. I've posted on the subject once per quarter since is starting happening in 2.0.5. machine1# rsh machine2 machine2# exit then on machine2 issue the command machine2# netstat -a | more near the top will be a session related to rshd. After 30 or so seconds the session will disappear from 'netstat -a' and you can then rsh from machine1 to machine2 again. -- Brian Litzinger Powered by FreeBSD http[s]://www.mpress.com