# qlist mariadb | grep systemd /usr/lib/systemd/system/mariadb@.service /usr/lib/systemd/system/mariadb.service /usr/lib/systemd/system/mariadb@bootstrap.service.d/use_galera_new_cluster.conf /usr/include/mysql/private/my_systemd.h /usr/share/mysql/systemd/mariadb@.service /usr/share/mysql/systemd/mariadb.service /usr/share/mysql/systemd/use_galera_new_cluster.conf (also note duplicate install) # qlist mysql-init-scripts | grep systemd /usr/lib/systemd/system/mysqld@.service /usr/lib/systemd/system/mysqld.service So I end up with at least two conflicting scripts to start mariadb. Both lack Conflicts= entry, so I can end up trying to start both ;-P.
MariaDB now includes notify support so that script should be preferred over the mysql-init-scripts one. I'll look into the Conflicts= but know little about systemd. Perhaps I'll just modify mysql-init-scripts with it or do I need to do both?
Adding it to one of them should be enough.
Fixed with dev-db/mysql-init-scripts-2.1_rc1 The instanced version must be done by the user as there is no universal way to Conflicts all iterations of an instanced service. Those using mariadb should prefer mariadb.service to have better notification support and not some script checking startup status. This is particularly nice for Galera cluster replication.
