Hi,

as of mariadb 1:11.8.9+ds-3, mariadb uses /run/mariadbd instead of
/run/mysqld. What used to be /run/mysqld/mysqld.sock is present as
/run/mariadbd/mysqld.sock now (note the mixture of mariadb + mysql
in the file name, with the underlying process also being
/usr/sbin/mariadbd).

I don't see the rational (the "why we're doing this") in neither
https://github.com/MariaDB/server/pull/5059/changes/2e711651ef977ed957656472287a4a775e219b3c
nor
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/178/diffs?commit_id=a4415e1fd71bee58d94202bd6c90715dcddf57d7
for this change, but the change as it is feels a bit inconsistent to me.

I'm aware that with mariadb-server-compat one gets /run/mysqld
back with its symlink to /run/mariadbd, and then
/run/mysqld/mysqld.sock is available as it used to be, but maybe
we've an option to also move /run/mariadbd/mysqld.sock into
/run/mariadbd/mariadbd.sock, to get this at least consistent?

Note: the change caused regressions in several scripts/services at
customers of mine, and looking at
https://codesearch.debian.net/search?q=%2Frun%2Fmysqld&literal=1&perpkg=1
there might be further software that might need adjustments.
Please consider mentioning this change with the option for
mariadb-server-compat at least in the release notes of forky.

PS: in the package description of mariadb-server-compat there's a
typo ("switcing" should be "switching"), maybe you could also fix
that. (I didn't want to provide a MR for this trivial change, since
its's triggering a build with lots of resource usage.)

regards
-mika-