Date: Fri, 02 May 2003 10:14:36 -0300 From: "Daniel C. Sobral" <dcs@tcoip.com.br> To: Lucky Green <shamrock@cypherpunks.to> Cc: mark@grondar.org Subject: Re: save-entropy "route: not found" Message-ID: <3EB26F3C.9020109@tcoip.com.br> In-Reply-To: <00cf01c30fb7$36745010$6601a8c0@VAIO650> References: <00cf01c30fb7$36745010$6601a8c0@VAIO650>
next in thread | previous in thread | raw e-mail | index | archive | help
Lucky Green wrote:
>>"Lucky Green" writes:
>
> [...]
>
>>$ man rc.conf # check out the second paragraph.
>
>
> I am a moron.
Not necessarily. (Mind you, I'm not saying you are _not_, just that that
doesn't follow from this :)
We have /etc/rc.local for commands you need to run. Now, it _seems_
natural to put commands in /etc/rc.conf, since that file is sourced. It
might get to seem less natural if one notes in how many places it is
actually sourced. One gets to entertain serious doubts about the wisdom
of doing that when one considers the possible need of sourcing it during
normal operation, just to get the settings while doing things with one
subsystem (like running /etc/rc.d/named restart, for example). But it
only breaks down when someone explains that rc.conf is actually a
configuration file, and that the configuration is read by the artifact
of sourcing it is a mere implementation detail.
Alas... what would people think of setting PATH to something
non-existent when sourcing rc.conf?
--
Daniel C. Sobral (8-DCS)
Gerencia de Operacoes
Divisao de Comunicacao de Dados
Coordenacao de Seguranca
VIVO Centro Oeste Norte
Fones: 55-61-313-7654/Cel: 55-61-9618-0904
E-mail: Daniel.Capo@tco.net.br
Daniel.Sobral@tcoip.com.br
dcs@tcoip.com.br
Outros:
dcs@newsguy.com
dcs@freebsd.org
capo@notorious.bsdconspiracy.net
Mene, mene, tekel, upharsen.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EB26F3C.9020109>