From owner-freebsd-arch Mon Sep 18 22:20:11 2000 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id BA31537B423; Mon, 18 Sep 2000 22:20:08 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id BAA40167; Tue, 19 Sep 2000 01:19:55 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 19 Sep 2000 01:19:55 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Warner Losh Cc: "Brian F. Feldman" , Alfred Perlstein , arch@FreeBSD.org, sjr@home.net Subject: Re: sysctl on boot. In-Reply-To: <200009172043.OAA25218@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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