Date: Mon, 17 May 2004 10:53:57 -0700 From: Freddie Cash <fcash-ml@sd73.bc.ca> To: <Barbish3@adelphia.net> Cc: questions@freebsd.org Subject: Re: Manually starting RCng scripts disabled in rc.conf Message-ID: <200405171053.57758.fcash-ml@sd73.bc.ca> In-Reply-To: <MIEPLLIBMLEEABPDBIEGCEFOFOAA.Barbish3@adelphia.net> References: <MIEPLLIBMLEEABPDBIEGCEFOFOAA.Barbish3@adelphia.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 17, 2004 10:16 am, JJB wrote: > There are no knobs in rc.conf for the applications you mentioned. > Rc.conf does not have internal check to verify you have correct > statements. So having apache_enable="YES" in rc.conf does nothing > and issues no error message telling you it is invalid. All ports > are started from /usr/local/etc/rc.d/ This is true only for non-RCng scripts that have the generic case statement with start/stop options. For instance, the www/apache13 port prior to around 1.3.29_4 used the old rc-style script. After that, it uses an RCng script which requires an entry in rc.conf to activate. Read through the comments in /usr/ports/www/apache13/files/apache.sh if you don't have it installed to see what I mean. RCng scripts require an entry in /etc/rc.conf along the lines of <appname>_enable="YES" otherwise the script will fail to do anything. This works great for starting scripts at boot time as everything is configured / controlled via one central file. However, it's more of a pain than anything when you don't want the app to start at bootup, but want to start the app manually later on. There are workarounds by changing the name of the startup script or editing rc.conf. I'm just wondering if there is anything built into RCng for this situation. Please CC: me as I'm not sub'd to questions@. -- Freddie Cash fcash-ml@sd73.bc.ca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405171053.57758.fcash-ml>