[debian-mysql] Bug#742900: Bug#742900: [Pkg-systemd-maintainers] No mysqld.service File

[Clint Byrum]

Excerpts from Michael Stapelberg's message of 2014-03-31 10:47:34 -0700:
> Hi merc,
> 
> merc1984 at f-m.fm writes:
> > On Fri, Mar 28, 2014, at 16:16, Michael Biebl wrote:
> >> You can certainly depend within a .service file on a sysv init script
> >> 
> >> Since the SysV init script is named /etc/init.d/mysql, you'd have to use
> >> something like
> >
> > That's very nice in theory, but I am telling you in practice it does not
> > work.  That's why I'm having to go to all this trouble.
> “It does not work” is not a proper description of a problem. As you seem
> to be convinced that this is broken, may I ask you to file a bug report
> against systemd? That will include more information (state dump) to
> start with. Also, please increase the log level to “debug” — see
> https://wiki.debian.org/systemd#Debugging — and provide the output of
> journalctl -b.

It is more likely that it is a problem with the mysql sysvinit script
and mysqld itself. What is probably wrong is that mysqld is daemonizing
and returning control to the terminal before it is _actually_ ready.

Note that in Ubuntu the upstart job for mysqld runs it in the foreground,
and the post-start _polls mysqld_ so that anything that wants to be
'start on started mysqld' will have a working mysqld.

Still, I would appreciate the "it doesn't work" full description too.