Date: Mon, 05 Feb 2001 01:02:41 -0800 From: Doug Barton <DougB@FreeBSD.org> To: Lars =?iso-8859-1?Q?K=F6ller?= <Lars.Koeller@uni-bielefeld.de> Cc: freebsd-bugs@FreeBSD.org, lkoeller@cc.fh-lippe.de Subject: Re: conf/22151: source mechanism of /etc/rc.conf* files Message-ID: <3A7E6C31.84073F4@FreeBSD.org> References: <200102050633.HAA08040@hermes.hrz.uni-bielefeld.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Lars Köller wrote:
> > Yes, there was a good reason for this change. /etc/defaults/rc.conf
> > is sourced from many different locations at many different times (not
> > just at boot). It should be a pure configuration file.
>
> Hmmm, thats not the problem, it's still a pure configuration file if it
> respects user changes recorded in /etc/rc.conf!
The old system had a shell code bit at the end of /etc/defaults/rc.conf
that did the sourcing of /etc/rc.conf[.local] itself. This makes it not
purely a configuration file, and caused problems when it was sourced from
other times and other places than the startup scripts. It also caused big
problems for users who just copied the default file to /etc/ because the
script would recursively source itself until the system ran out of file
descriptors. Bad mojo all the way around.
> At the moment i can't imagine where it is usefull only to have the
> DEFAULT config available not respecting user changes! What do I
> miss?
Your own description of the solution in your PR. Include a call to the
source_rc_confs function in your scripts that need the configuration
variables. All of the freebsd scripts have been modified long ago, so you
have plenty of examples.
Good luck,
Doug
--
"Pain heals. Chicks dig scars. Glory . . . lasts forever."
-- Keanu Reeves as Shane Falco in "The Replacements"
Do YOU Yahoo!?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A7E6C31.84073F4>