From owner-freebsd-hackers Fri Sep 26 01:05:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA19268 for hackers-outgoing; Fri, 26 Sep 1997 01:05:41 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19263 for ; Fri, 26 Sep 1997 01:05:38 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id BAA17565; Fri, 26 Sep 1997 01:05:36 -0700 (MST) From: Terry Lambert Message-Id: <199709260805.BAA17565@usr04.primenet.com> Subject: Re: rc.sysctl? To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Fri, 26 Sep 1997 08:05:36 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Jaye Mathisen" at Sep 25, 97 10:17:53 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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? > > There doesn't seem to be any good place to put them. > > rc.local is too late, since things like keepalive, send/recvspace, and > others may need to be set before things like sendmail start up. > > 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). Heh. And you are proposing a mechanism which is tantamount to /etc/conf on Solaris, only you can't drop in new configuration code by dropping in a new file, you have to instead modify a file that contains both instructions and the configuration data that they operate on. Sounds a hell of a lot like the BSD rc file vs. rc.d argument to me. ;-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.