I just set up a master/slave replication scheme and all is well,
but through the procedure did get bit on the tail.
After the setup, and after the master and slave mysql servers
had been started, I got some error messages that pointed to
a type in the slave's my.cnf file. I shut the slave down,
fixed the typo, and restarted. Got the same error.
I had a look at the master.info, and noticed it contained
old information from the previous my.cnf. There were no
binary log entries in it, so I shut the slave down, deleted
the master.info, and restarted the slave. This fixed the
problem and they're replicating fine. (A terrific feature,
my thanks to the mysql team for that one.)
Question is, is this behaviour by design? Seems to me if
you edit my.cnf and restart the mysql slave the master.info
entries corresponding to the my.cnf file should be updated.
Thanks for any insight.
Mike Robinson
IT / Developer - Toronto Star TV
Phone: 416.945.8786
Fax: 416.869.4566
Email: [EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
