I am setting up replication between two machines using MySQL 5.5 EE on Linux. The master will be on prod1 and the slave db will be on dr1. The machines share nothing (different /usr/local, different domain, etc).
I want some settings to be the same on both machines (such as memory, data dir, etc), but obviously there will be some differences between the two.
I know I can do this setup with two my.cnf files and having the common settings duplicated in each file. For efficiency sake, I would like to place the common settings in something like a my.common file, and the db specific ones in the my.cnf and having the my.cnf somehow reference the my.common file.
I know in the oracle world the concept is an "ifile", but I don't know if the same exists in the MySQL world.
I was thinking of trying to get the --defaults-extra-file to do this, but it doesn't seem to work the way I want (or I'm not using it correctly).
Am I on the right track with the --defaults-extra-file, or is two my.cnf files just the better way to do it? What's the common convention?
I want some settings to be the same on both machines (such as memory, data dir, etc), but obviously there will be some differences between the two.
I know I can do this setup with two my.cnf files and having the common settings duplicated in each file. For efficiency sake, I would like to place the common settings in something like a my.common file, and the db specific ones in the my.cnf and having the my.cnf somehow reference the my.common file.
I know in the oracle world the concept is an "ifile", but I don't know if the same exists in the MySQL world.
I was thinking of trying to get the --defaults-extra-file to do this, but it doesn't seem to work the way I want (or I'm not using it correctly).
Am I on the right track with the --defaults-extra-file, or is two my.cnf files just the better way to do it? What's the common convention?
