Date: Fri, 26 Sep 1997 17:03:25 +0930 From: Mike Smith <mike@smith.net.au> To: Jaye Mathisen <mrcpu@cdsnet.net> Cc: hackers@freebsd.org Subject: Re: rc.sysctl? Message-ID: <199709260733.RAA00370@word.smith.net.au> In-Reply-To: Your message of "Thu, 25 Sep 1997 22:17:53 MST." <Pine.NEB.3.95.970925221354.28045r-100000@mail.cdsnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Can anybody think of a good reason not to have something like > /etc/rc.sysctl that contains any sysctl -w's that you want to have run > before you start up a bunch of daemons? Yes. Nothing other than rc.conf should contain parameters (with the dubious exception of rc.local). > There doesn't seem to be any good place to put them. rc.conf is where the values should go. > rc.local is too late, since things like keepalive, send/recvspace, and > others may need to be set before things like sendmail start up. These are network parameters, and thus should be set in rc.network. They should be keyed off the existence of variables set in rc.conf, which could be supplied as NO by default. > Seems trivial to add, and potentially useful. > > (Of course, run levels ala solaris would solve this problem as well, but > that's another argument for another time and place). No, they further distribute and obfuscate the configuration information. You might want to consider a more generalised sysctl tweaking mechanism , eg. one that consumed variables of the form 'sysctl_X' where X was a monotonically increasing value starting with 0. You could handle these early on in rc, just after rc.conf is sourced. This would still suffer from the "sysctl is not in /sbin" problem for people using NFS for /usr. mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709260733.RAA00370>