From owner-freebsd-current Tue May 7 08:36:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA14909 for current-outgoing; Tue, 7 May 1996 08:36:02 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA14874 Tue, 7 May 1996 08:35:57 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.6.12) with ESMTP id IAA26963; Tue, 7 May 1996 08:34:28 -0700 (PDT) Message-Id: <199605071534.IAA26963@austin.polstra.com> To: imb@scgt.oz.au Cc: randy@zyzzyva.com, winter@jurai.net, freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: MBUFs leaking? In-reply-to: <199605061718.DAA26465@asstdc.scgt.oz.au> Date: Tue, 07 May 1996 08:34:28 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Butler writes: > > I've had a similar problem. However, I hadn't noticed any correlation > > with NMBCLUSTERS. Try rolling back your pmap.c to the -RELEASE version. > > That "solved" the problem for me. > > Are you running with the associated new ld.so ? If not, try installing it > instead of backing out pmap.c, Ld.so is not associated with pmap.c. There's no reason to try to keep them in sync. The recent update to the -stable version of ld.so simply brought in a bunch of stuff that has been in -current for months and months. The only halfway-new feature is the LD_PRELOAD support, and even that has been in -current for a couple of weeks at least. Also, somebody else suggested that the -current version of ld.so was somehow more solid than the one in -stable. That seems unlikely, since the two are identical at this time. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth