From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 18:42:07 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0FAD716AA7D for ; Thu, 11 Jan 2007 18:42:07 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id B46A513C45A for ; Thu, 11 Jan 2007 18:42:06 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 25252 invoked by uid 399); 11 Jan 2007 18:42:06 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 11 Jan 2007 18:42:06 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A684FC.4070609@FreeBSD.org> Date: Thu, 11 Jan 2007 10:42:04 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061215) MIME-Version: 1.0 To: Lamont Granquist References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> <45A566D7.4040907@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Use of /etc/rc.conf.d (Was: Re: LDAP integration) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 18:42:07 -0000 Lamont Granquist wrote: > > On Wed, 10 Jan 2007, Doug Barton wrote: >> It's not documented, but the code is there in /etc/rc.subr: >> >> grep 'rc.conf\.d' /etc/rc.subr >> if [ -f /etc/rc.conf.d/"$_name" ]; then >> debug "Sourcing /etc/rc.conf.d/${_name}" >> . /etc/rc.conf.d/"$_name" >> ... > > If i understand that correctly its not *exactly* what i was looking for, > but its better than a monolithic /etc/rc.conf > > It looks like you must put /etc/rc.d/inetd config into either > /etc/rc.conf or /etc/rc.config.d/inetd. Actually you can use both, but where variable names overlap whatever is sourced last will "win." > That means that if you've got two different orthogonal applications > runing on the same server which both need to run something orthogonal > out of inetd then they still wind up needing to do edits to the same > config file to get inetd configured correctly. Not exactly (and I think you're overusing the term orthogonal). :) rc.conf and /etc/rc.conf.d only store configuration for the rc.d scripts themselves. The configuration of inetd is still stored in /etc/inetd.conf. $ grep inetd /etc/defaults/rc.conf inetd_enable="NO" # Run the network daemon dispatcher (YES/NO). inetd_program="/usr/sbin/inetd" # path to inetd, if you want a different one. inetd_flags="-wW -C 60" # Optional flags to inetd vs. everything that is in /etc/inetd.conf. > I'd rather see > /etc/rc.config.d/app01 and /etc/rc.config.d/app02 both able to tweak > inetd settings. Of course there is the possibility that app01 and app02 > could drop mutually conflicting inetd setttings, but you've got that > problem anyway in the existing scheme... I think this'd be great, I can't wait to see your patches. :) Doug -- This .signature sanitized for your protection