We derive the package from Debian, and in Debian multiple init systems are supported. So the package does need to ship all three. In Debian the user could switch between init systems and reboot, and the package and associated service should continue to work.
I appreciate that this could be confusing in that you might thing that an init.d script is active when in fact the system is running upstart (or systemd) and so not using it, but that is how the packaging currently works. If that should be changed, it needs to be addressed as part of a larger effort - there is nothing we can do specifically in MySQL packaging to make it less confusing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521771 Title: Shutdown timeout values are inconsistent between init.d, upstart and systemd init scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1521771/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
