Date: Thu, 1 Feb 2001 19:17:19 +0100 From: Thomas Moestl <tmoestl@gmx.net> To: freebsd-hackers@freebsd.org Subject: Re: removing setgid kmem from top, collecting per-device swap stats Message-ID: <20010201191719.A703@crow.dom2ip.de> In-Reply-To: <20010202.022829.04064803.ume@mahoroba.org>; from ume@mahoroba.org on Fri, Feb 02, 2001 at 02:28:29AM %2B0900 References: <20010130224759.A1589@crow.dom2ip.de> <20010201171135.O70673@hand.dotat.at> <20010202.022829.04064803.ume@mahoroba.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 02, 2001 at 02:28:29AM +0900, Hajimu UMEMOTO wrote: > >>>>> On Thu, 1 Feb 2001 17:11:35 +0000 > >>>>> Tony Finch <dot@dotat.at> said: > > dot> Thomas Moestl <tmoestl@gmx.net> wrote: > > > >Most kmem_read calls are easy to replace (the variables are already > >exported as sysctls), the only exception is nextproc (for which I might > >add a sysctl, or just leave it out [anyone out there who needs the > >lastpid display?]). > > dot> It's useful for seeing how fast the machine is forking. > I beleive it's not meaningful if randompid is enabled. It is. It gives the greatest pid used up to now. The next pid is determined by adding 1 (and randomness in the randompid case) to it. This is why I can export it without defeating randompid. Of course, it would still be better to track the sysctls you named for this, but people seem to like the lastpid dispay, so I won't remove it for now. - thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010201191719.A703>