469,106 Members | 2,185 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,106 developers. It's quick & easy.

mysqld_safe not so safe!

running mysqld_safe --help to check the options for mysqld_safe, and
instead of a warning or an error or hell no, "help". it deletes the
mysql.sock for the currently running instance and tells me it cannot
start. this isn't particularly helpful or "safe". i would have though
the something that includes the word "safe" might actually be ...
somewhat safe.

perhaps checking to see if the command line is valid, and if there is
an instance already running before deleting the mysql.sock file, maybe
even a warning "hey i am going to remove this, is this ok" which could
be disabled via a command line option.

from the man page

"mysqld_safe adds some safety features such as restarting the
server when an error occurs and logging run-time information to a log
file."

it would be handy if they had added a few more.

sorry, now i have to figure out when i can shutdown these databases to
recreate the mysql.sock file.

end rant

c
Jul 20 '05 #1
0 1228

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Craig A. Falls | last post: by
1 post views Thread by Roger Lord | last post: by
9 posts views Thread by Jody Gelowitz | last post: by
1 post views Thread by jecheney | last post: by
4 posts views Thread by George2 | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by kglaser89 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.