Re: [RFC][Change-Request] Create usefulness in rc.subr etc/rc.conf.d/*.conf namespace.

Hi,

2011/5/8 Jason Hellenthal <jhell_at_dataix.net>

>
> List, - Please reply-to freebsd-rc_at_freebsd.org
>
> What does it do ?: As stated above, current functionality is undisturbed
> while allowing the user to create config's by any name they so desire as
> long as it has an extension of ".conf", also introducing the ability to
> turn a configuration file off by using chmod(1). You can turn nfsc1.conf
> off/on by simply chmod [-/+]x etc/rc.conf.d/nfs1.conf
>

seams not to be included in your patch, unless you change the line (or i'm
wrong):
if [ -f "$_modular_conf" ]; then
by
if [ -x "$_modular_conf" ]; then


>
>
> Why ? Simple. How many times have you been bitten by disabling something
> in the rc.conf file and left to discover what you just disabled was also
> used by another daemon but that daemon is now not starting ? This is a way
> to virtualize your configuration allowing you to add multiple _enable=
> lines to different configurations for different roles. For instance
> rpcbind is used by both samba and nfs*. With this you can add
> rpcbind_enable to both a configuration for samba and nfs and when you
> disable one service you know that you have not disabled a dependent for
> another.
>

i resolved that by making multiple files source the same conf file.

today my biggest problem is bad rc.d script
like apache22, postfix, clamd or haproxy who load_rc_config and after
overwrite extra_commands variable.
this prevent me to add extra commands from a /etc/rc.conf.d/$name file.