When emerging mysql 4.0.24 the /var/run/mysqld folder that was created was owned by root:root, not mysql:mysql. I unmerged and re-emerged, with the same results. Reproducible: Always Steps to Reproduce: emerge mysql /etc/init.d/mysql start Actual Results: Mysql complained about not being able to bind to a socket, it wouldn't start, had to be zapped. /var/run/my Expected Results: Mysql should have started normally
Are you using mythbackend?
See comment #1.
Not as far as I am aware, this was just after a clean gentoo 2005.0 install, I rebooted and: `emerge sun-jdk samba mod_php tomcat jboss` I used the i686 stage 3 tarball and the following make options: CFLAGS="-O3 -march=athlon -fomit-frame-pointer" MAKEOPTS="-j2" USE="-gtk -gnome -X -qt -kde -cdr -cups xml xml2 innodb oc gd ssl mysql apache2 jpeg png doc jikes" (I think oc is a typo, but it's in there anyway :P)
Hmm, pretty strange, the ebuild seems to be OK... <snip> pkg_postinst() { mysql_get_datadir #empty dirs... [ -d "${ROOT}/${DATADIR}" ] || install -d -m0750 -o mysql -g mysql ${ROOT}/var/lib/mysql [ -d "${ROOT}/var/run/mysqld" ] || install -d -m0755 -o mysql -g mysql ${ROOT}/var/run/mysqld [ -d "${ROOT}/var/log/mysql" ] || install -d -m0755 -o mysql -g mysql ${ROOT}/var/log/mysql </snip> Is this broken just in stage 3?
Before that I installed the athlon-xp stage 3 and it worked alright..
Seem fixed to me, washing all the bug I can I wish to close this one too ;)