https://bugzilla.novell.com/show_bug.cgi?id=223209 ------- Comment #7 from lenz@grimmer.com 2006-11-24 00:28 MST ------- Thanks for making me aware of this! In the future, please also raise such issues on our packagers@lists.mysql.com mailing list. This avoids me to be the bottleneck/SPOF, if I am not around... I agree that using "mysqladmin shutdown" is currently not the best solution, as it requires the mysql root user password. For now, I'd prefer if you would use an approach similar to ours, that simply gives mysqld some more time to remove it's PID file after it received SIGTERM before you shoot it in the head. We haven't heard of any problems with the value of 35 seconds we choose for our script. 60 seconds should really get you on the safe side. So the proposed change attached to comment#3 is fine with me. I like the idea of having some kind of admin socket, I will add this to our feature tracker. But it may be already obsolete since we introduced the mysqlmanager, which is supposed to replace the current mysqld_safe wrapper script. It is in charge of starting and stopping mysqld instances (but currently probably suffers from the same problem of requiring a password by default). Once 10.2 is out the door (which is looking great, btw! I was not able to report anything for 10.2b2...), I'd like to recommend you to take a look at it. Our init scripts have already modified to support it. Please see http://dev.mysql.com/doc/refman/5.0/en/instance-manager.html for the general overview. My blog entry at http://www.planetmysql.org/entries/2108 gives you a quick start in how to enable it. The instance manager will be enabled by default for MySQL 5.1 and up. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.