Date: Wed, 10 Feb 1999 09:22:09 -0800 (PST) From: David Wolfskill <dhw@whistle.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: suggestion for modular system configuration Message-ID: <199902101722.JAA02400@pau-amma.whistle.com> In-Reply-To: <199902101557.KAA01257@cs.rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>Date: Wed, 10 Feb 1999 10:57:57 -0500 >From: "David E. Cross" <crossd@cs.rpi.edu> [Lots of elisions -- dhw] > if chkconfig inetd; then > /usr/sbin/inetd > fi >when chkconfig is run it looks for a file named /etc/config/$argv[1], that >file simply contains one word 'on' or 'off'. If the file contains 'on', >chkconfig returns true, 'off' false. >I propose that we adopt this system, with a couple of modifications that will >make it even more powerfull and usefull. Have an optional variable >'CHKCONFIGPATH', that would behave similarly to 'XUSERFILESEARCHPATH' with >respect to haveing some optional '%' expansions. >Here is a preliminary idea: >%N _N_ame, equal to what is passed in argv[1]. >%H _H_ost, fqdn. >%h _h_ost, hostname. >A CHKCONFIGPATH path element that had no '%' expansions in it would default to >ending with '/%N'. A reasonable default CHKCONFIGPATH may well be: >/etc/config/%N:/usr/local/etc/config/%h/%N:/usr/local/etc/config/%N >-or perhaps- >/etc/config/%h/%N:/etc/config/%N:/usr/local/etc/config/%h/%N:/usr/local/etc/config/%N >(the occurance in the path 'wins'). The idea, dissimilar though it may be to traditional BSD practice, certainly has its attractions. I believe that providing an ability to do a "dry run" (to see what would be started/stopped, and in what order, but without actually starting or stopping processes) would be quite useful. (I tend to do this sort of thing with the Perl scripts that I write, for example.) >This would be a huge win for us here as we have a shared /usr/local, and >with putting 'httpd.sh' in /usr/local/etc/rc.d as well as netatalk.sh and >others we have had to do some special things to get only certain packages >to run on certain hosts (it usually involves sucking in the entire rc.conf >for EVERY SINGLE rc-file... as is already done by the system rc-files. *yuck*) I can empathize with that, certainly.... Cheers, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902101722.JAA02400>