Redhat 6.1 Linux MySQL 1.2215 I'm doing a mysqldump with --flush-logs, and mysql is getting the update logs confused - I tested this when there *were* updates going on at the time of the dump. The docs said that on Linux the default is --skip-locking - what can I do to solve this update log confusion at flush-logs time? Can locking be enabled on a Linux system? How? Will this solve my update log confusion with flush-logs? Is there a way to to manually locking in the script that does the mysqldump? TIA. -- Hardy Merrill Mission Critical Linux, Inc. http://www.missioncriticallinux.com --------------------------------------------------------------------- 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
