From owner-freebsd-stable@FreeBSD.ORG  Sat Jan 31 19:07:05 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9FB5816A4CE
	for <stable@FreeBSD.org>; Sat, 31 Jan 2004 19:07:05 -0800 (PST)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ACC2A43D2F
	for <stable@FreeBSD.org>; Sat, 31 Jan 2004 19:07:04 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i1136u7E096266;
	Sat, 31 Jan 2004 19:07:00 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200402010307.i1136u7E096266@gw.catspoiler.org>
Date: Sat, 31 Jan 2004 19:06:56 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: rschi@rsmba.biz
In-Reply-To: <20040201023742.GA10388@foghorn.dmz.rsmba.biz>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: stable@FreeBSD.org
Subject: Re: SSH strangeness on 4.9
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2004 03:07:05 -0000

On 31 Jan, Richard Schilling wrote:
> I've had similar issues connecting via SSH to a solaris box.  I thought 
> it was related to the job I was running on the Solaris box, but never 
> did find the answer.  In my case when I exit from the other box the 
> connection seems to hang.  The only way to completely terminate is to 
> kill the ssh process.

I've run into that with Solaris as well.  At least in the case of
Solaris it is not a problem specific to FreeBSD, since I was connecting
from a Linux client.