Manually starting RCng scripts disabled in rc.conf
Peter Risdon
peter at circlesquared.com
Mon May 17 10:40:21 PDT 2004
Dan Nelson wrote:
>In the last episode (May 17), Freddie Cash said:
>
>
>>Is it possible to manually run an rcNG-style script with
>>app_enable=NO in /etc/rc.conf?
>>
>>For instance, there are a few services that I don't want running all
>>the time on my laptop (like Apache, Squid, DansGuardian) but that I
>>need running now and then for development / testing purposes. As
>>such, I have apache_enable="NO" in my rc.conf to prevent Apache from
>>starting at boot time. However, this also means that I cannot
>>manually start Apache when I need it running, unless I use apachectl
>>or run the httpd binary directly. And I can't use the RCng script to
>>check the status, or restart, or any of the other nice things that
>>RCng gives me. It would be much simpler/nicer if I could use the
>>rcNG script to do this.
>>
>>Am I missing something simple, or is it just not possible to do what
>>I want? I'd like to use the rc.d scripts to control everything, but
>>if I have to enable them all in rc.conf and then manually stop them
>>after each boot, I'll most likely end up writing my own non-RCng
>>wrapper scripts for each app. :(
>>
>>
>
>"forcestart" should do what you want, I think.
>
>
>
In similar situations, I change
/usr/local/etc/rc.d/whatever.sh
to
/usr/local/etc/rc.d/whatever.sh.notnow
(or any other suffix) so it doesn't start at boot time, then start it up
when I want with
#/usr/local/etc/rc.d/whatever.sh.notnow start
and stop it again in the obvious way. I'd be interested to know what the
drawbacks to this approach are.
PWR.
More information about the freebsd-questions
mailing list