Another way you can do something similar, rather than messing around with permissions is to use the read-only option. This option exists in MySQL 4.0+. It prevents anyone except for the mysql root user or the replication thread from being able to change data -- regardless of their permissions. You can even set it on the fly with something like: SET GLOBAL read_only = 1;
Regards, Harrison On Tue, 16 Mar 2004, cvarda wrote: > I'm currently replicating all databases, so this would happen. > > This means that I should change my setup to do not replicate the 'mysql' > database. > > Is there a way to explicity do not replicate only 'mysql' and replicate all > others, including new databases? > > []s, > Conrado > > > ----- Original Message ----- > From: "Alan Williamson" <[EMAIL PROTECTED]> > To: "cvarda" <[EMAIL PROTECTED]> > Sent: Tuesday, March 16, 2004 5:30 PM > Subject: Re: Blocking INSERT/UPDATE on SLAVE (replication) > > > > > > > > cvarda wrote: > > > > > But this wouldn't conflict with 'mysql' database replication? Changes on > the > > > master users would override my setup on the slave... am I wrong? > > > > > > yes you are wrong :) > > > > you only mirror/replicate certain DATABASES, not the whole server. > > Therefore you wouldn't not mirror the 'mysql' database as this would > > then cause the problems you describe. Only mirror the database with > > your real data > > > > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
