From owner-freebsd-current@FreeBSD.ORG  Sat Oct  9 08:38:07 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 84A7416A4CE
	for <freebsd-current@freebsd.org>;
	Sat,  9 Oct 2004 08:38:07 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3976843D46
	for <freebsd-current@freebsd.org>;
	Sat,  9 Oct 2004 08:38:07 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i998adaY004294;
	Sat, 9 Oct 2004 04:36:40 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)i998adjA004291;
	Sat, 9 Oct 2004 04:36:39 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Sat, 9 Oct 2004 04:36:39 -0400 (EDT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
In-Reply-To: <20041009031904.GA68861@parodius.com>
Message-ID: <Pine.NEB.3.96L.1041009043526.93055C-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: Bizarre network+ssh+bash shell behaviour
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Oct 2004 08:38:07 -0000


On Fri, 8 Oct 2004, Jeremy Chadwick wrote:

> On one of my boxes -- and only that box -- hitting EOF (^D) in bash
> to log out results in no printed "logout" message.  The socket does
> get closed cleanly, and the pty/tty does get put back into the
> "allocatable pty/tty pool" (sorry, not familiar with this portion).
> However, normally when logging out of a shell, the time between logout
> and the time between the actual socket being dropped is minimal (i.e.
> immediately); in the case of the "weird box", there is a good 1-2
> second delay before the actual socket is dropped.

It would probably be interesting to run tcpdump on one or both boxes and
see if anything in particular stands out.  I.e., a FIN gets sent and the
other follows much later or the like.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Principal Research Scientist, McAfee Research