Just started using mylvmbackup and encountered this exact error as soon as I enabled innodb_recover. Thanks for the patch John. Would be nice to have this bug fixed in Hardy. I guess it does not have catastrophic consequences, but can result in slower recovery from the generated backup.
According to app changelog [http://www.lenzg.net/mylvmbackup/ChangeLog] this bug was fixed by author between versions 0.7 and 0.8 on 2008-03-03. -- innodb_recover calls mysql with wrong pid file argument https://bugs.launchpad.net/bugs/253192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
