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> Cc: freebsd-current@freebsd.org Subject: Re: memguard monitoring of more than 1 memory_type? Message-ID: <20060207190121.GF19674@comp.chem.msu.su> In-Reply-To: <20060207183152.GA50629@troutmask.apl.washington.edu> References: <20060207183152.GA50629@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060207190121.GF19674>