Starting with Ubuntu 9.10, and presisting through today's daily ISO of Lucid, services which use lsb start_daemon to start their service, start_daemon does not fork off the daemon process WHEN THE SERVICE IS STARTED AT BOOTUP. However, killing the daemon process which in turn clears up the hung start script to clean up the environment - then starting the service interactively, the start script runs cleanly through to completion.
I have opened a bug against this behavior against 9.10, and also verified that versions of Lucid do it, up through today's daily ISO.
Does anyone know of other software which uses lsb start_daemon to start services so I could compare if also affects other packages using lsb start_daemon?
What is different DURING BOOT TIME that lsb start_daemon is unable to fork the daemon process, but once booted it forks properly and completes the script?
Here is my bug report:
"Suddenly start_daemon does not fork the new pid, hangs the script"
I have checked and the other two start service methods the start script looks for do not come as part of Ubuntu, so lsb start_daemon is the only choice it seems on Ubuntu to start the service.