Comment 13 for bug 1319595

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since we use systemd in Ubuntu now (since 15.04), this bug no longer applies to the development release so I'm marking it Fix Released.

For upstart-using stable releases that are still supported, I don't think it's inappropriate to change the upstart script to not use --nodaemonize in an update automatically recommended to users as that will change behavior and thus clearly has the potential to regress users.

In terms of changing to the init.d script, you are welcome to do this by modifying or deleting the upstart and init.d scripts as appropriate as a workaround. They are in /etc and so packaging will attempt to preserve your changes by Debian policy. Given that you have to deleted the upstart job, it seems reasonable to me that you also have to manually edit the init.d script to enable it even if upstart is running.

But in any case, we can't fix this in Trusty for all users due to the regression risk, a workaround is available and the bug no longer applies with systemd in the development release for the future. Since there is no longer any work to do on this bug, Fix Released is appropriate.