On Fri, Apr 16, 2004, David M. Fetter wrote: > On Fri, 2004-04-16 at 00:08, Ralf S. Engelschall wrote: >> On Thu, Apr 15, 2004, David M. Fetter wrote: >>> [...] >>> I have exactly the following at the end of my rc.conf file: >>> >>> openpkg_rc_def=no >>> dhcpd_enable=yes >>> >>> Therefore, if I'm understanding this correctly, only dhcpd should start >>> on boot, right? That's not what is happening. Am I doing this wrong? >>> >> As you can see, openpkg_rc_def is initialized to "yes", then your >> rc.conf sets it to "no", then things like amd_enable and dhcp_enable >> become "no" and then your rc.conf overrides dhcpd_enable to "yes". Use >> this --print debugging yourself and try to find out where the difference >> is for you, please. >> > It seems as if the rc.conf is not passing the variable settings to rc > properly. I can't see any reason why not though. If I do rc --config > it does show there that all services state enable=no, but the output of > rc --print all start shows them all enabled and still starts them all. > Does 'rc --print dhcpd start' produce the following line?
. /cw/etc/rc.conf That's where your custom variables are loaded, and it should occur just before the common (implicit) and command (explicit) sections use the variables in their script bodies. If the problem continues, then like Ralf suggested you might try printing the whole output of the rc command that is failing. -- [EMAIL PROTECTED] Development Team, Operations Northern Europe Cable & Wireless Telecommunications Services
pgp00000.pgp
Description: PGP signature
