Yeah, I notice this too, especially after upgrading to MAX. I really find it annoying.
My guess is that the RPM is slightly different than the God given RH version, so there are TWO KXXmysqld in /etc/rc.d/init.d or in one of the rc.3 or rc.5 or something and so one shuts it down, then the other executes and it fails b/c it was already shut down. I sooo wish the person that packages that RPM would fix this. Same with the mysql-max issue. It creates a mysql instead of mysqld (or vise versa), and it doesn't have that nice: "Loading mysql [ok]" style thing, it just barfs some ugly text instead. Eeek! > -----Original Message----- > From: Karen Tan [mailto:[EMAIL PROTECTED] > Sent: Monday, March 10, 2003 4:53 PM > To: [EMAIL PROTECTED] > Subject: MySQL Shutdown FAILED > > > > > I have just upgraded from MySQL 3.23.32 to 3.23.55 on my > RedHat 8 server. > Everything is working fine except that I get FAILED for > MySQL when shutting down. > I have not changed any settings at all. And the FAILED message does > not seem to affect anything with MySQL operations. How do I > go abt checking what is causing > the message? Someone pls help! Thanx. > > -Karen --------------------------------------------------------------------- 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
