Re: Feature Request: /usr/local/etc/rc.conf support

"slave-mike" <slave-mike_at_slavepix.com> writes:

> as /et/rc.conf is sourced as a shell script archive could one
> put something like ...
>
> if [ -x /usr/local/etc/rc..conf ]; then
>     . /usr/local/etc/rc.conf
> fi
>
> in /etc/rc.conf ???

That would work, but you would still have the overriding important
settings problem.

> ----- Original Message ----- 
> From: "Doug White" <dwhite_at_gumbysoft.com>
> To: "Ted Cabeen" <secabeen_at_pobox.com>
> Cc: <freebsd-current_at_freebsd.org>; <freebsd-ports_at_freebsd.org>
> Sent: Wednesday, February 18, 2004 9:10 PM
> Subject: Re: Feature Request: /usr/local/etc/rc.conf support
>
>
>> On Tue, 17 Feb 2004, Ted Cabeen wrote:
>>
>> > With the ever-increasing number of ports that use rc.conf variables to
>> > regulate their startup, would it be possible to add support for a
>> > /usr/local/etc/rc.conf file in FreeBSD?  The constant changes to the
>> > rc.conf file have been playing havoc with my centralized management
>> > systems, and it makes it harder and harder to keep the /etc/rc.conf
>> > file set immutable (which I like to do on critical servers, to prevent
>> > the securelevel from changing).
>>
>> I keep wanting to suggest using the already-existent /etc/rc.conf.local,
>> but now that you mention that you want to lock out changes to stuff like
>> securelevel, it makes more sense why you'd want to split it off.
>>
>> -- 
>> Doug White                    |  FreeBSD: The Power to Serve
>> dwhite_at_gumbysoft.com          |  www.FreeBSD.org
>> _______________________________________________
>> freebsd-current_at_freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>>
>
>

-- 
Ted Cabeen
Sr. Systems/Network Administrator
Impulse Internet Services