Re: Master will insist on running as a SLAVE if data/master.info exists. - Mikael Fridh - com.mysql.lists.mysql

4 messages in com.mysql.lists.mysqlRe: Master will insist on running as ...

From	Sent On	Attachments
Kevin A. Burton	29 Dec 2004 15:00
Mikael Fridh	30 Dec 2004 09:53
Kevin A. Burton	01 Jan 2005 23:17
Mikael Fridh	02 Jan 2005 05:46

Subject:	Re: Master will insist on running as a SLAVE if data/master.info exists.
From:	Mikael Fridh (mika...@ongame.com)
Date:	12/30/2004 09:53:46 AM
List:	com.mysql.lists.mysql

Kevin A. Burton wrote:

This is a bug.

Feature.

I have all the slave configuration in /etc/my.cnf commented out. However the machine was ONCE a slave and so data/master.info exists.

I commented out all the /etc/my.cnf settings WRT master-* yet when I restart the box it STILL insists on starting the slave via master.info

In fact, you don't need those configuration statements in the first place. You could just as well initiated the slave replication by issuing CHANGE MASTER TO...

If these settings aren't enabled the slave shouldn't be started.

Slave is always "started" unless my.cnf says "skip-slave-start". Anyway, WITH skip-slave-start you will still have the slave information (binlog positions etc.) initiated but it will just not start replicating.

The information in master.info overrides anything in my.cnf.