Date: Wed, 17 Jan 2001 01:30:12 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: msmith@FreeBSD.ORG (Mike Smith) Cc: mckusick@mckusick.com (Kirk McKusick), arch@FreeBSD.ORG Subject: Re: dynamic vs static sysctls? Message-ID: <200101170130.SAA19626@usr08.primenet.com> In-Reply-To: <200101160727.f0G7Rss00920@mass.osd.bsdi.com> from "Mike Smith" at Jan 15, 2001 11:27:54 PM
next in thread | previous in thread | raw e-mail | index | archive | help
> > I would think that this might be an issue for > > any application that uses sysctl to get/set the same information > > repeatedly. > > It is. It's also useful in the case where you use trailing fields in the > MIB to pass arguments to the sysctl handler. It's also useful for externalizing a sub-arc opaquely for standard sub-arcs. For example, the Network Interface Monitoring MIB contents, being externalized via systctl to a user space SNMP implementation, and recast in generic form, not dependent on the FrBSD OID-arc. This also has the benefit of standardizing SNMP consoles, as well as letting us standardize between BSD's, without playing "dueling OID-arc origins" (e.g. "BSDI" vs. "FreeBSD" vs. "NetBSD" vs. "XXX" is not a problem, if you can just point at an RFC and smile). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101170130.SAA19626>