From owner-freebsd-current@FreeBSD.ORG  Wed Jun  2 07:25:21 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 B1E8216A4CE; Wed,  2 Jun 2004 07:25:21 -0700 (PDT)
Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 3658243D2F; Wed,  2 Jun 2004 07:25:21 -0700 (PDT)
	(envelope-from frode@nordahl.net)
Received: from [195.159.148.126] (dhcp7.xu.nordahl.net [195.159.148.126])
	by smtp1.powertech.no (Postfix) with ESMTP
	id 1EC1C8094; Wed,  2 Jun 2004 16:25:20 +0200 (CEST)
In-Reply-To: <20040602141712.GB33162@freefall.freebsd.org>
References: <20040602141712.GB33162@freefall.freebsd.org>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <AB46CE64-B4A0-11D8-A18D-000A95A9A574@nordahl.net>
Content-Transfer-Encoding: 7bit
From: Frode Nordahl <frode@nordahl.net>
Date: Wed, 2 Jun 2004 16:25:16 +0200
To: Bosko Milekic <bmilekic@FreeBSD.org>
X-Mailer: Apple Mail (2.618)
cc: freebsd-current@FreeBSD.org
Subject: Re: [HEADS-UP] mbuma is in the tree
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: Wed, 02 Jun 2004 14:25:21 -0000


On Jun 2, 2004, at 16:17, Bosko Milekic wrote:
>   I'm afraid you misunderstood what I meant by "Giant leak." :-)

*whoops* :-)

>   Please cvsup to -CURRENT (follow the -current mailing list to figure
>   out when it should be reasonably safe to do so) and verify whether 
> this
>   problem has been fixed, as it is posssible that it already has.

Not sure if I dare do this on the production server, but I will set up 
a test system to see if I can reproduce and test against -CURRENT.

Thanks for your response

Cheers,
Frode

>
>   -Bosko