From owner-freebsd-current  Mon Jun 24 21:12:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA04394
          for current-outgoing; Mon, 24 Jun 1996 21:12:31 -0700 (PDT)
Received: from multivac.orthanc.com (root@multivac.orthanc.com [207.102.89.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA04384
          for <current@freebsd.org>; Mon, 24 Jun 1996 21:12:28 -0700 (PDT)
Received: from localhost (lyndon@localhost) by multivac.orthanc.com (8.7.5/8.7.3) with SMTP id VAA07543; Mon, 24 Jun 1996 21:12:09 -0700 (PDT)
Message-Id: <199606250412.VAA07543@multivac.orthanc.com>
X-Authentication-Warning: multivac.orthanc.com: Host lyndon@localhost didn't use HELO protocol
From: Lyndon Nerenberg VE7TCP <lyndon@orthanc.com>
To: "Jordan K. Hubbard" <jkh@time.cdrom.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 20:32:23 PDT."
             <199606250332.UAA16404@time.cdrom.com> 
Date: Mon, 24 Jun 1996 21:12:09 -0700
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

Replace rsh with rlogin if you like.

If so, this is a symptom of a long-standing bug (since 2.1-RELEASE at the
very least) related to reuse of addr/port pairs that I haven't been able
to track down. (And lots of other people have seen.)

XX is related to the FIN_WAIT timeout values.

--lyndon