From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 22:43:56 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 6B74C16A407; Wed, 10 Jan 2007 22:43:56 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.freebsd.org (Postfix) with ESMTP id 385FD13C455; Wed, 10 Jan 2007 22:43:56 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id l0AMhte9005823; Wed, 10 Jan 2007 14:43:55 -0800 (PST) Date: Wed, 10 Jan 2007 14:43:55 -0800 (PST) From: Lamont Granquist To: Doug Barton In-Reply-To: <45A566D7.4040907@FreeBSD.org> Message-ID: 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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Vulpes Velox Subject: 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: Wed, 10 Jan 2007 22:43:56 -0000 On Wed, 10 Jan 2007, Doug Barton wrote: > Lamont Granquist wrote: >> On Wed, 10 Jan 2007, Doug Barton wrote: >>>> And if you're looking specifically at the /etc/rc.conf config file, what >>>> would be more useful would be an /etc/rc.conf.d/ directory. >>> >>> Good news for you, we already support that. :) I agree that it makes a >>> great tool for the "many systems" problem, and could reasonably be >>> used for part of the "dynamic laptop" problem too. >> >> 7-current feature? I'm not seeing it in rc.conf(5) on my RELENG_6-ish >> system... > > 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. 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. 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... Basically I like self-containment around a top-down role that the server plays ('i am an ftp server') not necessarily around a bottom-up subsystem like inetd... YMMV.