Skip to main content


Since I moved server, I left behind my #Devuan install to restart from a #Debian 11 offered by my hosting provider which I immediately upgraded to Debian 12. This means I am back to #systemd land, and I'm already annoyed with it.

See, service mariadb [action] calls mariadb-admin that requires password-less root access (??) to localhost to do anything, which I don't allow for obvious security reasons.

On the other hand, systemctl [action] mariadb.service doesn't rely on mariadb-admin, but there's no graceful reload available either. 🤷‍♂️

I already miss /etc/init.d/mysqld [action].

#SysAdmining #SysAdmin

you could supress the service file and call directly mariadb tools

No idea what the init script did for reload, but you can add a drop in for the mariadb service file, e.g. assuming the init script sent a SIGHUP to the PID of mariadb you would write


[Service]ExecReload=/usr/bin/kill -s SIGHUP $MAINPID

to /etc/systems/system/mariadb.service.d/reload.conf

Just guessing the name of the service, more info about ExecReload in the systemd.service man page and about drop in config in systemd.unit

@Andy H3 I did that once and it served me well! I might do that again soon if it keeps annoying me. I was kind of hoping for a better experience with Debian 12, but the problem seem to be with systemd itself, I'm afraid.