This might be related to checking for crashed tables (ie poor interaction between debian-start and mysqld_safe). I noticed that mysql would not accept connections until the crashed tables operation was completed. mysqld_safe and /etc/init.d/mysql use mysqladmin to connect to the database, so there may be poor interaction here.
-- mysqd_safe high cpu usage https://bugs.launchpad.net/bugs/105457 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
