Date: Mon, 20 Mar 2006 07:09:10 -0800 From: Micah <micahjon@ywave.com> To: Jerry McAllister <jerrymc@clunix.cl.msu.edu> Cc: Bill Schoolcraft <bill@wiliweld.com>, freebsd-questions@freebsd.org Subject: Re: hosts.allow ? Message-ID: <441EC596.5040308@ywave.com> In-Reply-To: <200603201438.k2KEcXM4021508@clunix.cl.msu.edu> References: <200603201438.k2KEcXM4021508@clunix.cl.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Jerry McAllister wrote: >> At Sun, 19 Mar 2006 it looks like Jerry McAllister composed: >> >>> One doesn't start anything from the rc.conf file - at least properly. >>> Those things get started from /usr/local/etc/rc.d. >>> >>> What goes in /etc/rc.conf are environmental variable settings that >>> those rc.d scripts look at to determine what to do. >>> >> I was under the impression that when one 'restarts' that the >> service will "re-read" /etc/rc.conf > > I am not sure just at what point the rc.conf is read or re-read. > Try putting something in the /usr/local/etc/rc.d/xxxx.sh script to > check for a specific environmental variable that you make up and put > in /etc/rc.conf and then running the xxxx.sh script manually to see > what it knows about - even just put a printenv in the script. > > ////jerry From the source it's clear that rc.conf is read when the individual rc script executes a load_rc_config $name (or equivalent). HTH, Micah
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?441EC596.5040308>