Date: Sun, 17 Sep 2000 12:34:32 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Warner Losh <imp@village.org> Cc: arch@FreeBSD.ORG, sjr@home.net Subject: Re: sysctl on boot. Message-ID: <20000917123432.M15156@fw.wintelcom.net> In-Reply-To: <200009171904.NAA24354@harmony.village.org>; from imp@village.org on Sun, Sep 17, 2000 at 01:04:22PM -0600 References: <200009171904.NAA24354@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Warner Losh <imp@village.org> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000917123432.M15156>