Is --skip-lock-tables not an unsafe solution that might produce corrupt backups? Is it not better to simply stop mysql, mysldump, then start, if you prioritize backups over 247 uptime?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995587 Title: mysqldump: Got error: 1142: SELECT,LOCK TABL command denied to user 'debian-sys-maint'@'localhost' for table 'cond_instances' when using LOCK TABLES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/automysqlbackup/+bug/995587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
