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.
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
