Bug#407928: Not starting ffproxy due to option in /etc/default

2007-03-03 Thread Emmanuel Bouthenot
tag 407928 +wontfix thanks Hi, i tag wontfix and i suggest you to open a discussion on debian-devel mailing list to expose the behaviour you want to start daemons. As i have already explain, the solution is to use update-rc.d. For now, all the daemons works like this in debian. cheers, --

Bug#407928: Not starting ffproxy due to option in /etc/default

2007-01-30 Thread Armando Romero
Hello, I can always find solution for myself easily and thank you. It is also possible to install any software without Debian packaging. But this is bug for future Debian OS. I think you are right about using update-rc.d, as it shall be so:

Bug#407928: Not starting ffproxy due to option in /etc/default

2007-01-30 Thread Emmanuel Bouthenot
what do you think about adding an option 'force-start' in init script to start ffproxy even if FFPROXY_START=no in /etc/default/ffproxy ? cheers, -- Emmanuel Bouthenot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#407928: Not starting ffproxy due to option in /etc/default

2007-01-30 Thread Armando Romero
Hello, I think that one option could be used: START_ON_BOOT=no but script can be started AFTER the boot manually: /etc/init.d/ffproxy start because that is the reason to have the start stop script, right? If you think you want users to be able to disable start at all, you can have another

Bug#407928: Not starting ffproxy due to option in /etc/default

2007-01-30 Thread Emmanuel Bouthenot
because that is the reason to have the start stop script, right? no, init script is for the 'Unix System V' init. the way to start the daemon manually is to use the binary in /usr/bin and run it with the option you need. I agree that a common way is to use the init script to start/stop the

Bug#407928: Not starting ffproxy due to option in /etc/default

2007-01-29 Thread Emmanuel Bouthenot
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

Bug#407928: Not starting ffproxy due to option in /etc/default

2007-01-26 Thread Emmanuel Bouthenot
The ffproxy has option in /etc/default/ffproxy: # yes = start on boot; no = don't start on boot FFPROXY_START=no That is great option which shall prevent starting on boot. However, if that option is no, the script: /etc/init.d/ffproxy start gives: Not starting ffproxy - edit

Bug#407928: Not starting ffproxy due to option in /etc/default

2007-01-22 Thread Armando Romero
Package: ffproxy Version: 1.6-2 Severity: normal The ffproxy has option in /etc/default/ffproxy: # yes = start on boot; no = don't start on boot FFPROXY_START=no That is great option which shall prevent starting on boot. However, if that option is no, the script: /etc/init.d/ffproxy start