From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 06:08:33 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 8C4B216A403 for ; Thu, 11 Jan 2007 06:08:33 +0000 (UTC) (envelope-from fcash-ml@sd73.bc.ca) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5B40C13C442 for ; Thu, 11 Jan 2007 06:08:31 +0000 (UTC) (envelope-from fcash-ml@sd73.bc.ca) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 1E00A1A0007AC for ; Wed, 10 Jan 2007 21:37:11 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8rfZpXwV7-Rc for ; Wed, 10 Jan 2007 21:37:04 -0800 (PST) Received: from webmail.sd73.bc.ca (webmail.sd73.bc.ca [10.10.10.17]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 9B8651A000B2A for ; Wed, 10 Jan 2007 21:37:04 -0800 (PST) Received: from 24.71.119.183 (SquirrelMail authenticated user fcash) by webmail.sd73.bc.ca with HTTP; Wed, 10 Jan 2007 21:37:04 -0800 (PST) Message-ID: <63903.24.71.119.183.1168493824.squirrel@webmail.sd73.bc.ca> In-Reply-To: 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> Date: Wed, 10 Jan 2007 21:37:04 -0800 (PST) From: "Freddie Cash" To: freebsd-hackers@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Thu, 11 Jan 2007 12:41:32 +0000 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: Thu, 11 Jan 2007 06:08:33 -0000 On Wed, January 10, 2007 2:43 pm, Lamont Granquist wrote: > 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... To each their own, of course. Personally, I am so sick of the way system like Debian use dozens of config files for each app, all in their own conf.d/ sub-directories. Some apps, like PureFTPd actually use separate config files for each and every option it supports. Trying to configure these apps is a royal pain of opening and editing a dozen files. Maybe this makes it easier for automated configuration tools and GUIs, but it makes it a *ROYAL* pain in the arse for mere mortals using text editors to manage. What is wrong with 1 editable text file per app? With a single sub-directory per application for config files? Where you can quickly, and easily view all the options at a glance? The nicest thing about FreeBSD is /etc/rc.conf, a single configuration file that is easily editable in any text editor. Makes managing systems remotely so simple. ---- Freddie Cash, LPIC-2 CCNT CCLP Helpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] fcash@sd73.bc.ca helpdesk@sd73.bc.ca