The solution is ...
FLUSH PRIVILEGES;
on the slaves.
As it's not an UPDATE, this command is not sent to slaves with the binlog.
> -Original Message-
> From: BALU Frédéric [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 23, 2001 8:47 AM
> To: 'Stefan Hinz';
Already tried ... Not successfully.
Another idea ?
> -Original Message-
> From: Stefan Hinz [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 20, 2001 7:51 PM
> To: BALU Frédéric; [EMAIL PROTECTED]
> Subject: Re: help needed for replication
>
>
> Dear Frede
Hi everybody,
I use Replication on a windows NT4 Server.
There are 1 master and 2 slaves, all on the same machine.
One slave is started with the option skip-name-resolve, not the other.
For the 2 slaves : master-host=localhost
When adding a user (MYSQL.User), the replication is OK but,
when
Hi everybody,
I use Replication on a windows NT4 Server.
There are 1 master and 2 slaves, all on the same machine.
One slave is started with the option skip-name-resolve, not the other.
For the 2 slaves : master-host=localhost
When adding a user (MYSQL.User), the replication is OK but,
when
Hi everybody,
I use Replication on a windows NT4 Server.
There are 1 master and 2 slaves, all on the same machine.
One slave is started with the option skip-name-resolve, not the other.
For the 2 slaves : master-host=localhost
When adding a user (MYSQL.User), the replication is OK but,
when
