Hi Jehan,
OK so it seems to be a bad idea ... I was expecting that I missed a
magic command like "set readonly on all databases" ...
I think you did:
SET GLOBAL read_only=1;
This will keep all non-SUPER and non-replication users from writing to
the database.
Regards,
Jeremy
--
high pe
put this in your my.cnf
"read_only"
this would put the DB in a read only mode, except for the slave threads and
the super users, which/who can still do writes, this option is mostly used
on slaves though .
see http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html
Kishore Jalle
OK so it seems to be a bad idea ... I was expecting that I missed a
magic command like "set readonly on all databases" ...
however, still thinking in a probably bad solution , what about setting
unix file system acces mode to the database files to read only (400)
wouldn't be a good idea ? (if I
I personally would be wary of a solution like what you're proposing
(locking all tables, that is).
The problem I see is this - you lock all tables and proceed to move
your data over to another host. Meanwhile, clients could well be
queueing up insert or update commands that are simply blocking,
Instead of "locking" the table, why not just change the privileges for the specific accounts so they have select only privileges?
Then you still of write access through "admin" accounts if need be.
- Original Message -
From: "Jehan PROCACCIA" <[EMAIL PROTECTED]>
To:
Sent: Friday, June
