Your message dated Sun, 22 Nov 2020 17:10:44 +0200
with message-id
<CAHj_TLCaAYF+7BLK6tYei-+Wu9G=azetkimm5o8xewdfmty...@mail.gmail.com>
and subject line Re: [debian-mysql] Bug#852776: Bug#852776: marked as done
(mariadb-server-10.1: init script doesn't specify it should be started prior to
apache2 etc)
has caused the Debian Bug report #852776,
regarding mariadb-server-10.1: init script doesn't specify it should be started
prior to apache2 etc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
852776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852776
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-server-10.1
Version: 10.1.21-2
Severity: normal
I note in the postinst that it says
update-rc.d mysql defaults 19 21
with the explanation given in debian/rules that this is so the mysqld
server begins before apache. However, with dependency-based boot
systems (which current installations are by default), the "19 21" no
longer has any effect: insserv only looks at the dependency
information in its header. In fact, on my system, because of the
dependencies on the various init scripts (which are just the default
Debian ones), apache2 comes in at S04apache2 while mysql comes in at
S05mysql!
To specify that mysql really should start prior to apache2 (and
presumably nginx as well; not sure what other servers), you would need
lines:
X-Start-Before: apache2
X-Stop-After: apache2
in the header of /etc/init.d/mysql.
But I don't see any dependency of apache2 on mysqld in its normal
configuration, and if a particular installation of apache2 does
require mysqld to be started in advance, then it is up to the sysadmin
of that system to add:
Should-Start: mysql
Should-Stop: mysql
to their instance of /etc/init.d/apache2 (or whatever other
appropriate init.d file).
So my suggestion is just to drop the "19 21" from the debian/rules so
as not to give the false impression that mysql is starting earlier.
Best wishes,
Julian
--- End Message ---
--- Begin Message ---
Closing this issue now as there was now further information supplied
and there is nothing we as package maintainers can do about this, and
if was for mariadb-10.1 anyways.
On Sat, 22 Aug 2020 at 14:21, Otto Kekäläinen <[email protected]> wrote:
>
> Hello!
>
> If this issue is still relevant, and you have a suggestion how to fix
> it, please file a Merge Request on Salsa as a proposal. Thanks!
>
> https://wiki.debian.org/Teams/MySQL/patches
>
> _______________________________________________
> pkg-mysql-maint mailing list
> [email protected]
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-mysql-maint
--
- Otto
--- End Message ---
