Deployment of /etc/init.d/mysql causes issues

Hi,

I have found that recent versions of MariaDB 10.3 deploy a /etc/init.d/mysql start script. On AlmaLinux 8, this script is automatically imported as a systemd service called "mysql". On earlier versions, the 'mysql' service was aliased to 'mariadb'.

This causes two issues:

1: The script starts the 'mysql' service, not the MariaDB service. Therefore stopping the mariadb service does not work after starting the mysql service. This might sound trivial, but automated management runs into issues this way when someone manually intervenes.

2: The start script starts mariadb with log-error to a file, instead of to syslog. This is non-default behaviour.

I propose to remove the /etc/init.d/mysql script as I don't see how it adds value.

Thanks,
Michaël