The init.d script provided with the MySQL RPMs has a problem: if an
application depends on MySQL (say, it's a daemon logging some data in
MySQL), and this application starts right after MySQL, it usually fails.
The reason is, when the init.d/mysql script returs, usually MySQL is not
fully running, but it's still initializing some stuff. If the other
application has its init.d script right after, it fails to connect to
the database, because the database does not run yet. Depending on the
application, then the application itself might fail to start altogether.
Please add a delay (like "sleep 2" or something like that) to the start
function in the init.d script. Or modify the start function to not
return until MySQL has booted up properly. Like:
while [it didn't started yet]; do
sleep 1
done
--
Florin Andrei
"You can get excited about just any subject if you study it enough.
It's the deep knowledge that makes a topic interesting." - Larry McVoy
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
