It is not bug in start-stop-daemon but in the script belonging to ffproxy. 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. Emmanuel Bouthenot wrote: > Hi, > > It's not a ffproxy bug but a bug in start-stop-daemon as described in > bugs reports #157305 and #352554. > > It's an old bug not yet fixed. I've added some informations and ask > the status for this bug (see > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352554#119). > > I hope this will be fixed for etch release. > > cheers, > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
