Wednesday, May 22, 2002, 9:23:02 AM, louie wrote: lm> Hi, i was thingking about locking the tables first so no connection lm> could write so i can do myisamchk. Is this process safe?
lm> Procedures: lm> 1. lockdb lm> 2. run myisamchk -r or -o lm> 3. unlock db lm> Btw, mysqld is running. I want to off it but i can't its a production lm> server. lm> Hope anyone could give me more info. Personally, I find the behavior of myisasmchk to be a bit "beta" when it comes live tables. It would be real easy for myisasmchk to refuse to run when mysqld is running. That should be a built-in precaution. I can understand possible objections to myisasmchk globally locking tables out of the blue (it might disrupt what some clients are doing), but if myisamchk cannot run on a live table, it should not run on a live table. As simple as that. - Mark --------------------------------------------------------------------- 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
