From owner-freebsd-net@FreeBSD.ORG  Mon Nov 10 12:03:54 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id E79FF16A4CE; Mon, 10 Nov 2003 12:03:54 -0800 (PST)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E877C43F85; Mon, 10 Nov 2003 12:03:51 -0800 (PST)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hAAK27Mg060804;
	Mon, 10 Nov 2003 15:02:07 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)hAAK27kk060801;
	Mon, 10 Nov 2003 15:02:07 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Date: Mon, 10 Nov 2003 15:02:07 -0500 (EST)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: Andre Oppermann <oppermann@pipeline.ch>
In-Reply-To: <3FAFE2D0.F2FC77D7@pipeline.ch>
Message-ID: <Pine.NEB.3.96L.1031110150010.59199J-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-net@FreeBSD.org
cc: fenner@FreeBSD.org
Subject: Re: Current problem reports assigned to you
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Nov 2003 20:03:55 -0000

On Mon, 10 Nov 2003, Andre Oppermann wrote:

> FreeBSD bugmaster wrote:
> > 
> > Current FreeBSD problem reports
> > Critical problems
> > Serious problems
> > Non-critical problems
> > 
> > S  Submitted   Tracker     Resp.       Description
> > -------------------------------------------------------------------------------
> > o [2002/05/04] kern/37761  net         process exits but socket is still ESTABLI
> > 
> > 1 problem total.
> 
> What is going on with this? It comes up every other week.

freebsd-net has been set as the owner for the PR, and gnats will send a
weekly reminder e-mail that the problem report is still open until such
time as it gets closed (or suspended, I suspect).  Sometimes when a
specific owner for a problem hasn't been found, or is considered
undesured, mailing lists are assigned ownership of PRs (i.e., threads@, et
al).  Speaking of dangling PRs, and since we're talking generally about
multicast, does anyone know if we're going to make progress on kern/58359? 
It sounded like this change did get picked up by Apple, but I haven't
checked to see if it was picked up by other *BSD as well. 

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Network Associates Laboratories