Comment 9 for bug 530779

> The first is the kind of daemon that forks early, but then maintains communication with the parent so that the parent can exit
> with an appropriate exit code in case of error (rather than the kind which only fork once they are ready). These kinds aren't
> ready until the parent exits, not at the point of the fork. Since upstart follows the fork, it will think they are ready "too early"

Waiting until the parent dies will not work in cases such as squid, where the parent never dies.

A more appropriate solution would be to add the possibility to track by pidfile (to be specified in /etc/init/<service>.conf)