Date: Thu, 04 Jun 1998 15:32:07 -0700 From: Mike Smith <mike@smith.net.au> To: Nate Williams <nate@mt.sri.com> Cc: dyson@FreeBSD.ORG, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: kernfs/procfs questions... Message-ID: <199806042232.PAA02556@dingo.cdrom.com> In-Reply-To: Your message of "Thu, 04 Jun 1998 17:32:17 MDT." <199806042332.RAA05525@mt.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > But users aren't expected to use gdb/nm/hexdump, but sysctl is. Many of > > > these parameters *should* be tweaked to get better performance, avoid > > > errors, etc... > > > > > Only some of them, if any. > > Again I say, if they're not meant to be touched, then don't expose > them. It's stupid to expose something that is useless for 99.9% of the > population. They're no more or less "exposed" than, say, the diskslice ioctls. If they serve a function as (eg.) maintenance tools, then they're superior to the Sun "just use adb on the kernel and set this to that..." approach. > It's not my place to enforce, but if it were I'd start removing any > sysctl's that weren't documented/used. As Mike pointed out in private > email, there are 434 sysctl nodes in our system, and 20 of them are > documented one way or the other. The rest are magic. > > I think of sysctl as a bunch of big global variable, or OPTIONS in the > kernel config file. If it isn't documented, it isn't needed. > > Do I have permission to start removing sysctl's that aren't > documented/used? I would be more inclined to suggest an evenhanded review; if you can't obtain documentation on one, then hash it out with UNDOCUMENTED_SYSCTLS and wait for someone to complain. Silence would sound like acceptance to me. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com 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?199806042232.PAA02556>