From owner-freebsd-arch Sun Sep 17 12:34:36 2000 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0397737B422 for ; Sun, 17 Sep 2000 12:34:35 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8HJYWl16793; Sun, 17 Sep 2000 12:34:32 -0700 (PDT) Date: Sun, 17 Sep 2000 12:34:32 -0700 From: Alfred Perlstein To: Warner Losh Cc: arch@FreeBSD.ORG, sjr@home.net Subject: Re: sysctl on boot. Message-ID: <20000917123432.M15156@fw.wintelcom.net> References: <200009171904.NAA24354@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200009171904.NAA24354@harmony.village.org>; from imp@village.org on Sun, Sep 17, 2000 at 01:04:22PM -0600 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Warner Losh [000917 12:04] wrote: > > Stephen Roznowski reports in PR conf/19629 that there's a weakness in > /etc/rc.sysctl. As it stands now, it runs early in the boot process. > And it needs to run early in the boot process for many sysctls. > However, there is a problem. If you modload a driver or module after > this point, any variables set early in the boot process will not be > effective (because the setting fails). > > A short term fix is to just rerun /etc/rc.sysctl at the end of the > boot sequence, just before the secrelevel change. Stephen's PR > suggests this with a patch. I think it is good, but wanted to get > some feedback from others before doing this. > > A long term fix might be to give the kernel a memory so it can > initialize the sysctls from the get go. However, that's much harder > to pull off and a whole lot more work. > > Comments? This is potentially dangerous as i'm not sure all sysctls are idempotent (sp?) meaning setting them twice can have weird effects, a solution might be to add another rc.sysctl2 or rc.sysctl.modules or something. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message