Date: Tue, 19 Sep 2000 01:19:55 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: Warner Losh <imp@village.org> Cc: "Brian F. Feldman" <green@FreeBSD.org>, Alfred Perlstein <bright@wintelcom.net>, arch@FreeBSD.org, sjr@home.net Subject: Re: sysctl on boot. Message-ID: <Pine.NEB.3.96L.1000919011801.40151A-100000@fledge.watson.org> In-Reply-To: <200009172043.OAA25218@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 17 Sep 2000, Warner Losh wrote: > I don't think there are any non-idempotent sysctls that people would > be setting from rc.sysctl. However, I think I'm leaning towards > a second parameter to /etc/rc.sysctl. The first one would be > /etc/sysctl.conf and the second would be /etc/sysctl.modules.conf over > the short term. There are some idempotent sysctls that might be relevant -- in particular, ones relating to security that disable features. For example, you'll find that if you set kern.suser_permitted to 0, no further sysctl's can be set. As such, it is not idempotent, and ordering is very important :-). You could argue, however, that the setting of that variable belongs in an ordered rc event. I'd be tempted to have rc.sysctl run only at the end of /etc/rc processing, and as other sysctls have ordering requirements, to indicate that they should be placed strategically in /etc/rc and others such that they make sense, or set when appropriate modules are loaded. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services 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?Pine.NEB.3.96L.1000919011801.40151A-100000>