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