[Bug 1326428] [NEW] clash of upstart and sysvinit scripts

[Gertjan Oude Lohuis]

Public bug reported:

The mysql-server-5.6 installs two init-scripts: an upstart and a
sysvinit one:

* /etc/init/mysql.conf
* /etc/init.d/mysql

Ubuntu uses upstart to manage the mysql-daemon, but this doesn't keep
users from using /etc/init.d/mysql. This leads to confusing (and
dangerous?) situation:

$ sudo status mysql
mysql start/running, process 1683

$ pgrep mysqld
1683

$ sudo /etc/init.d/mysql status
[..]
Server version		5.6.17-0ubuntu0.14.04.1
Uptime:			8 min 30 sec
[..]

$ sudo /etc/init.d/mysql stop
 * Stopping MySQL database server mysqld                          [fail]

$ sudo status mysql
mysql start/running, process 3853

So, stopping mysql with '/etc/init.d/mysql stop' actually did work, but
upstart respawned the process like it should. This is very confusing.

Why does this package ship both init-scripts?

** Affects: mysql-5.6 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1326428

Title:
  clash of upstart and sysvinit scripts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1326428/+subscriptions