From owner-freebsd-current  Mon Jun 24 21:32:46 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA07877
          for current-outgoing; Mon, 24 Jun 1996 21:32:46 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA07868
          for <current@freebsd.org>; Mon, 24 Jun 1996 21:32:44 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id VAA16714; Mon, 24 Jun 1996 21:32:24 -0700 (PDT)
To: Lyndon Nerenberg VE7TCP <lyndon@orthanc.com>
cc: current@freebsd.org
Subject: Re: Has anyone noticed a problem with rshd in -current? 
In-reply-to: Your message of "Mon, 24 Jun 1996 21:12:09 PDT."
             <199606250412.VAA07543@multivac.orthanc.com> 
Date: Mon, 24 Jun 1996 21:32:24 -0700
Message-ID: <16712.835677144@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Does this happen according to the following scenario?
> 
> 	rsh foo blat
> 	[ drop connection and wait <XX seconds]
> 	rsh foo blat

No, unfortunately in this scenario even the first `rsh foo blat'
often fails.

				Jordan