From owner-freebsd-current@FreeBSD.ORG  Tue Feb  7 19:01:29 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: 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 8E23816A422
	for <freebsd-current@freebsd.org>; Tue,  7 Feb 2006 19:01:29 +0000 (GMT)
	(envelope-from yar@comp.chem.msu.su)
Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C826743D48
	for <freebsd-current@freebsd.org>; Tue,  7 Feb 2006 19:01:25 +0000 (GMT)
	(envelope-from yar@comp.chem.msu.su)
Received: from comp.chem.msu.su (localhost [127.0.0.1])
	by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id k17J1MKY048972;
	Tue, 7 Feb 2006 22:01:22 +0300 (MSK)
	(envelope-from yar@comp.chem.msu.su)
Received: (from yar@localhost)
	by comp.chem.msu.su (8.13.3/8.13.3/Submit) id k17J1LHQ048971;
	Tue, 7 Feb 2006 22:01:21 +0300 (MSK) (envelope-from yar)
Date: Tue, 7 Feb 2006 22:01:21 +0300
From: Yar Tikhiy <yar@comp.chem.msu.su>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-ID: <20060207190121.GF19674@comp.chem.msu.su>
References: <20060207183152.GA50629@troutmask.apl.washington.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060207183152.GA50629@troutmask.apl.washington.edu>
User-Agent: Mutt/1.5.9i
Cc: freebsd-current@freebsd.org
Subject: Re: memguard monitoring of more than 1 memory_type?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 07 Feb 2006 19:01:29 -0000

On Tue, Feb 07, 2006 at 10:31:52AM -0800, Steve Kargl wrote:
> Can memguard monitor the usage of more that one memory_type?

>From the memguard(9) manpage:

     Currently, MemGuard can only take over malloc(), realloc() and free() for
     a particular malloc type.

> I added 
>   vm.memguard.desc="filedesc"
>   vm.memguard.desc="DEVFS1"
>   vm.memguard.desc="ptys"
> to /boot/loader.conf under the assumption that all three
> types would be monitored.  However, I see
> 
> troutmask:kargl[207] sysctl -a | grep memg
> vm.memguard.desc: ptys
> vm.memguard.divisor: 10
> 
> which shows only the last loader.conf line is effective.

Each assignment to a tunable or sysctl overwrites
its former value, like in a programming language.

-- 
Yar