From owner-freebsd-current@FreeBSD.ORG  Tue Jun 22 11:12:18 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 92D3B16A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 22 Jun 2004 11:12:18 +0000 (GMT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7C3B943D4C
	for <freebsd-current@freebsd.org>;
	Tue, 22 Jun 2004 11:12:18 +0000 (GMT)	(envelope-from mux@freebsd.org)
Received: by elvis.mu.org (Postfix, from userid 1920)
	id 641635C868; Tue, 22 Jun 2004 04:12:18 -0700 (PDT)
Date: Tue, 22 Jun 2004 13:12:18 +0200
From: Maxime Henrion <mux@freebsd.org>
To: Dag-Erling Sm?rgrav <des@des.no>
Message-ID: <20040622111218.GS9228@elvis.mu.org>
References: <20040622092607.3661643D54@mx1.FreeBSD.org>
	<xzp1xk7x4r1.fsf@dwp.des.no> <20040622104924.GR9228@elvis.mu.org>
	<xzpwu1zvolz.fsf@dwp.des.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <xzpwu1zvolz.fsf@dwp.des.no>
User-Agent: Mutt/1.4.2.1i
cc: freebsd-current@freebsd.org
cc: Grover Lines <grover@ceribus.net>
Subject: Re: gdb
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: Tue, 22 Jun 2004 11:12:18 -0000

Dag-Erling Sm?rgrav wrote:
> Maxime Henrion <mux@freebsd.org> writes:
> > Given how the CVSup protocol works, monitoring with tcpdump is uneasy if
> > you don't know the protocol.
> 
> tcpdump will still show which side closed the connection.

We already know it's the server which is closing the connection from his
error message.

Maxime