I'm observing something with the mariadb package that looks very strange. When I try to initialize a fresh mysql db structure with "emerge --config dev-db/mariadb" after that command a mysqld process is running. However it is not started by the init script, "/etc/init.d/mysql status" shows "status:stopped". What makes it extra unusual is that the mysqld runs with the user of oidentd, a useraccount belonging to the oidentd daemon that I had once installed and have uninstalled. I.e. it runs with a useraccount that is unused and should have no relation whatsoever with the mariadb installation. I'm running a current ~amd64 system, mariadb version is 10.5.8.
Well, `/etc/init.d/mysql status` cannot be used to track anything from `emerge --config` action. Could you please show process details with used command-line so we can be sure it's really coming from config action?
Ok, sorry. Apparently this came somewhere else (from a docker container, not sure entirely what caused that but I believe it's an unrelated problem on my system, no gentoo bug), I just believed it was caused by emerge --config because it reappeared several times after I tried killing it and running emerge --config again. (I think it was just restarted on a regular basis.) Sorry for the noise.
