from #407929 --8<------------------------------------------- The user decides what shall be started on boot. This can be done by rcconf or update-rc.d on Debian system. For example, some users don't want apache to start on the root as that is how I like it.
But after the boot, it shall be possible to start the service by using: /etc/init.d/some_script Your script in the configuration /etc/default asks only if the script shall be started on boot. That is wrong, because if I say NO, I cannot start script AFTER THE BOOT without modifying the configuration. Either state in the configuration script /etc/default/something that you ask people if the ffproxy shall start at all, or enable the option in /etc/init.d/ffproxy that script can be started AFTER THE BOOT without modifying configuration, but not on BOOT as configured in /etc/default/ffproxy Do you get the idea? It is very logical to me. ---------------------------------------->8-- apache2 seems to be a wrong example because ffproxy init script works like apache2 one. Take a look at /etc/default/apache2, change its values and check the behaviour while starting or stoping apache with its init script. if you want to use ffproxy and not start it at boot then : be sure that 'FFPROXY_START=yes' in /etc/default/ffproxy, then run something like 'update-rc.d -f ffproxy remove'. cheers, -- Emmanuel Bouthenot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
