Hopefully that's enough info for you to decide whether you read it right.
But it looks like your slave had some issue with that. Do you have a lot
of privileges? One of the Google engineers told me he's sometimes seen
FLUSH PRIVILEGES break replication with a lot of privileges.
Whoever was doing that query should have been using GRANT and REVOKE
instead -- or DROP USER.
I'm the only one that gets in and does anything with the privileges. I
always do it with the root user as well, and most of the time, I just use
the MySQL Administrator to do that. However, because I was following
directions on setting up replication from the help file, I was just using
the MySQL Command line. But, I did not issue these commands, it may be that
I went into MySQL Administrator to look around or something, and ended up
changing something, but I'm not sure what it would have been. I don't
recall doing a DROP USER either. In fact, all of the user issues that I
did, I did on Friday night, and I haven't touched the users that I'm aware
of. I wasn't even in the system at all Saturday Night (I don't think).
Anyway. It's all a big mess and jumble. I think I'm going to attempt
re-syncing things and re-starting things tonight and trying to start fresh
again. I'll see what happens tomorrow.
Jesse
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
