Public bug reported: Currently the stop-slave documentation here:
http://docs.hollandbackup.org/provider_configs/mysqldump.html Still states: "...Suspending the slave does not change the backups, but does prevent the slave from spooling up relay logs. The default is not to suspend the slave (if applicable)." However, this was addressed in v1.0.6 as noted in CHANGES.txt: holland-mysqldump +++++++++++++++++ - holland-mysqldump now only stops the SQL_THREAD when stop-slave is requested So this is a minor documentation bug. ** Affects: holland-backup Importance: Undecided Status: New ** Changed in: holland-backup Milestone: None => 1.0.8 -- You received this bug notification because you are a member of Holland Build, which is subscribed to holland-backup. https://bugs.launchpad.net/bugs/810561 Title: mysqldump stop-slave documentation is out of date Status in Holland Backup Framework: New Bug description: Currently the stop-slave documentation here: http://docs.hollandbackup.org/provider_configs/mysqldump.html Still states: "...Suspending the slave does not change the backups, but does prevent the slave from spooling up relay logs. The default is not to suspend the slave (if applicable)." However, this was addressed in v1.0.6 as noted in CHANGES.txt: holland-mysqldump +++++++++++++++++ - holland-mysqldump now only stops the SQL_THREAD when stop-slave is requested So this is a minor documentation bug. To manage notifications about this bug go to: https://bugs.launchpad.net/holland-backup/+bug/810561/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~holland-coredev Post to : [email protected] Unsubscribe : https://launchpad.net/~holland-coredev More help : https://help.launchpad.net/ListHelp
