> I've asked -ports before whether it is suitable to let ports startup scripts
> honor /etc/rc.conf{,.local} settings by sourcing /etc/defaults/rc.conf and
> then running a source_rc_confs (or whatever is appropriate).
>
> This could be a solution to your problem - modify the ports' startup scripts
> to honor rc.conf options, then put appropriate enable/disable options
> in each machine's /etc/rc.conf or /etc/rc.conf.local.
>
> Attached is an example - a modification of the databases/mysql323-server
> port's startup script to honor a couple of mysqld_* variables from
> the RC script scheme.
>
> This approach has the disadvantage that the ports' startup scripts will
> have to be modified if the base system startup mechanism changes, or
> at least when the base system /etc/{defaults}/rc.conf{.local} parsing
> mechanism changes.
>
> G'luck,
> Peter
>
> --
> Do you think anybody has ever had *precisely this thought* before?
>
heh, it's called don't re-invent the wheel :-)
i actually was thinking more in fixing rc, when it goes through the rc.d/*.sh
it should check some rc.conf variable before running the script.
danny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
