home ~ # /etc/init.d/mysql start * ... * "/var/run/mysqld/mysqld.sock" is still present. * Please check that it's not owned by other servers and then remove it. [ !! ] home ~ # Sometimes when the PC is not shutdown properly ( crash, needing a hard reboot, power blackout... ) the socket file will remain behind. This should not prevent mysql from being started on next boot, but with the current init script it does. IMO the init script should either remove the socket by default or this should be made configurable. Having to manually remove the socket every once in a while is tedious.
(In reply to comment #0) > home ~ # /etc/init.d/mysql start > * ... > * "/var/run/mysqld/mysqld.sock" is still present. > * Please check that it's not owned by other servers and then remove it. > [ !! ] > home ~ # > > Sometimes when the PC is not shutdown properly ( crash, needing a hard reboot, > power blackout... ) the socket file will remain behind. This should not prevent When a database is shutted down badly, check and/or repair the tables is good advice. > mysql from being started on next boot, but with the current init script it > does. IMO the init script should either remove the socket by default or this > should be made configurable. > > Having to manually remove the socket every once in a while is tedious. > try NOCHECK=1 in /etc/conf.d/mysql , never tryed it on this circumstances but it should work.
(In reply to comment #1) > try NOCHECK=1 in /etc/conf.d/mysql , never tryed it on this circumstances but > it should work. Seems to work. Thanks.
conf.d/mysql cleaned