not adding daemons to rc.conf

[Chris Whitehouse]

Jona Joachim wrote:
> Jonathan Horne wrote:
>> ive noticed that apache can be started manually using the apachectl tool, even 
>> if it is not enabled in /etc/rc.conf.  do many other daemons have this 
>> ability?  i have a dev server that i would like to not have many things 
>> enabled in the rc.conf, but i would like an easy way to just start specific 
>> daemons when i need.
> 
> Take a look at /usr/local/etc/rc.d
> You will see several scripts belonging to server applications you
> installed. Each one of these scripts can start or stop the service.
> For example:
> /usr/local/etc/rc.d/apache.sh start
> /usr/local/etc/rc.d/apache.sh stop
> 
> When you put something into rc.conf it is actually this script that is
> executed, so every daemon that can be enabled in rc.conf can also be
> started/stopped using those scripts.

But the scripts check rc.conf so they still have to be enabled in 
rc.conf unless you use forcestart...

box# grep pf_enable /etc/rc.conf
box# pwd
/etc/rc.d
box# ./pf start
box# echo pf_enable=\"YES\" >> /etc/rc.conf
box# grep pf_enable /etc/rc.conf
pf_enable="YES"
box# ./pf start
Enabling pf.
No ALTQ support in kernel
ALTQ related functions disabled
No ALTQ support in kernel
ALTQ related functions disabled
box#

Chris