mirror of
https://github.com/MariaDB/server.git
synced 2025-02-20 04:15:35 +01:00

Partially reverts commit a4cc6fb91f
.
While all current versions of Linux have systemd, support for traditional
init.d is still needed e.g. on Linux subsystem on Windows, kFreeBSD and
special variants of Debian/Ubuntu that for other reasons don't have
systemd.
Thus, re-introduce the init file that was remove, but this time with
then name 'mariadb'.
Supporting traditional sysv init in paraller with systemd is easy, since
Debian has facilities for it.
Also simplify and update salsa-ci.yml install/upgrade testing works
for all previous MariaDB and MySQL releases without any excess quirks.
Note that in fresh installs the salsa-ci.yml needs to run command
'service mariadb status' to control the service, while on upgrades
it is enough to run 'service mysql status', since the init.d/mysql
file is left behind from previous install, along with some other
config files such as /etc/default/mysql and /etc/mysql/* stuff.
30 lines
2.1 KiB
Text
30 lines
2.1 KiB
Text
/etc/init.d/mariadb\[[0-9]+\]: [0-9]+ processes alive and '/usr/bin/mysqladmin --defaults-(extra-)?file=/etc/mysql/debian.cnf ping' resulted in$
|
|
/etc/init.d/mariadb\[[0-9]+\]: Check that mysqld is running and that the socket: '/run/mysqld/mysqld.sock' exists\!$
|
|
/etc/init.d/mariadb\[[0-9]+\]: '/usr/bin/mysqladmin --defaults-(extra-)?file=/etc/mysql/debian.cnf ping' resulted in$
|
|
/etc/mysql/debian-start\[[0-9]+\]: Checking for crashed MySQL tables\.$
|
|
mysqld\[[0-9]+\]: ?$
|
|
mysqld\[[0-9]+\]: .*InnoDB: Shutdown completed
|
|
mysqld\[[0-9]+\]: .*InnoDB: Started;
|
|
mysqld\[[0-9]+\]: .*InnoDB: Starting shutdown\.\.\.$
|
|
mysqld\[[0-9]+\]: .*\[Note\] /usr/sbin/mysqld: Normal shutdown$
|
|
mysqld\[[0-9]+\]: .*\[Note\] /usr/sbin/mysqld: ready for connections\.$
|
|
mysqld\[[0-9]+\]: .*\[Note\] /usr/sbin/mysqld: Shutdown complete$
|
|
mysqld\[[0-9]+\]: /usr/sbin/mysqld: ready for connections\.$
|
|
mysqld\[[0-9]+\]: .*/usr/sbin/mysqld: Shutdown Complete$
|
|
mysqld\[[0-9]+\]: Version: .* socket
|
|
mysqld\[[0-9]+\]: Warning: Ignoring user change to 'mysql' because the user was set to 'mysql' earlier on the command line$
|
|
mysqld_safe\[[0-9]+\]: ?$
|
|
mysqld_safe\[[0-9]+\]: able to use the new GRANT command!$
|
|
mysqld_safe\[[0-9]+\]: ended$
|
|
mysqld_safe\[[0-9]+\]: NOTE: If you are upgrading from a MySQL <= 3.22.10 you should run$
|
|
mysqld_safe\[[0-9]+\]: PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !$
|
|
mysqld_safe\[[0-9]+\]: Please report any problems at https://mariadb.org/jira$
|
|
mysqld_safe\[[0-9]+\]: See the manual for more instructions.$
|
|
mysqld_safe\[[0-9]+\]: started$
|
|
mysqld_safe\[[0-9]+\]: The latest information about MariaDB is available at$
|
|
mysqld_safe\[[0-9]+\]: the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be$
|
|
mysqld_safe\[[0-9]+\]: To do so, start the server, then issue the following commands:$
|
|
mysqld_safe\[[0-9]+\]: /usr/bin/mysqladmin -u root -h app109 password 'new-password'$
|
|
mysqld_safe\[[0-9]+\]: /usr/bin/mysqladmin -u root password 'new-password'$
|
|
usermod\[[0-9]+\]: change user `mysql' GID from `([0-9]+)' to `\1'$
|
|
usermod\[[0-9]+\]: change user `mysql' shell from `/bin/false' to `/bin/false'$
|