Actually, this is an Upstart issue, which I can confirm as of Upstart 0.6.5-4.
/etc/init.d/mysql is merely a symlink for the general file /lib/init/upstart-job, which use the same case to catch both reload and force-reload, using the variable COMMAND to refer to the actual command being used.
Not sure if the solution is to teach initctl about force-reload or if /lib/init/upstart-job should be rewritten to give a more proper response.
Actually, this is an Upstart issue, which I can confirm as of Upstart 0.6.5-4.
/etc/init.d/mysql is merely a symlink for the general file /lib/init/ upstart- job, which use the same case to catch both reload and force-reload, using the variable COMMAND to refer to the actual command being used.
Not sure if the solution is to teach initctl about force-reload or if /lib/init/ upstart- job should be rewritten to give a more proper response.