[debian-mysql] Bug#765425: Bug#765425: mysql-server-5.5: mysql-sever lacks a systemd .service file.

[Clint Byrum]

Excerpts from Thayne Harbaugh's message of 2014-10-14 16:39:04 -0700:
> Package: mysql-server-5.5
> Version: 5.5.39-1
> Severity: normal
> 
> Dear Maintainer,
> 

Hi Thayne. Thanks for taking the time to report a bug. It is much
appreciated and your thoughts are valued.

>    The mysql-server-5.5 .deb lacks a systemd .service file.
> 
>    * What led up to the situation?
> 
>      Saltstack (salt-master .deb) is unable to manage mysql-server on
>      a system running systemd.  A /lib/systemd/system/mysql.service
>      file will address this.
> 

Salt is broken then. There are _thousands_ of perfectly good working
sysvinit scripts. Ansible is quite capable of managing a hybrid system,
perhaps copy their approach?

>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
>      Potentially the salt systemd module can be expanded to manage
>      services running in SysVinit compatibility mode.  Some simple
>      tweaks of the salt module were insufficient.
> 
>      The /etc/init.d/mysql script is more sophisticated than most.  It
>      does not lend itself to a simple .service implementation.
> 

Agreed on all points.

>    * Additional information:
> 
>      There is a similar Fedora bug that has been addressed and closed:
> 
>        https://bugzilla.redhat.com/show_bug.cgi?id=714426
> 
>      It appears this was addressed with a combination of a .service
>      file as well as some additional scripts.
> 

I know that your intentions, and those of the Fedora developers above
are well meaning. However, IMO this is mostly a waste of time. MySQL is
an application, and isn't going to be part of early-boot plumbing any
time soon. So having a systemd service is entirely for style points.