In file mysql-multilib.eclass at lines 801 through 804 contains: # Secure the logfiles touch "${ROOT}${MY_LOGDIR}"/mysql.{log,err} chown mysql:mysql "${ROOT}${MY_LOGDIR}"/mysql* chmod 0660 "${ROOT}${MY_LOGDIR}"/mysql* In my special case I did "ln -s /var/lib/mysql /var/log" to make the log files shown up in /var/log/mysql. This probably not a good idea, but I tried it. Every time I emerged mysql (maridadb) it would fail to start. The chmod line above prevents mysql from starting because the mysql database directory can not be accessed. The permissions on the /var/lib/mysql directory (that contains the actual mysql database GRANTS etc.) were changed from 0700 to 0660. I know this was caused by my symbolic link, but is is preventable... Add a "." to the chmod like this: chmod 0660 "${ROOT}${MY_LOGDIR}"/mysql.* ^ so it does not match "mysql"
(In reply to Wilson M. Michaels from comment #0) > In my special case I did "ln -s /var/lib/mysql /var/log" to make the log > files shown up in /var/log/mysql. This probably not a good idea, but I > tried it. > > Every time I emerged mysql (maridadb) it would fail to start. The chmod > line above prevents mysql from starting because the mysql database directory > can not be accessed. The permissions on the /var/lib/mysql directory (that > contains the actual mysql database GRANTS etc.) were changed from 0700 to > 0660. > If you want to move the logs in your configuration, do so in my.cnf. Setting a symlink is the wrong thing to do.
