<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Warren:<br><br><blockquote type="cite">I've inherited a complex LAMP application.<br></blockquote><br>Well the below MySQL commands would lead me to believe that some of the complexity is needless. <br><br><blockquote type="cite">A script runs nightly to dump the databases for a backup. After the<br>dumps and before emailing the results, the script issues the following<br>commands on each database:<br><br>mysql -u <user> -p<password> -h <DB Server> -e "reset master"<br>mysql -u <user> -p<password> -h <DB Server> -e "flush logs"<br></blockquote><br>As it takes a root equivalent user to issue these commands and a host has been specified I would say that you should look into performing a security audit of at least your MySQL part, and probably the whole stack. <br><br>"reset master" really serves no useful purpose, unless there is some other script that makes use of the fact that the binary log is now .000001 position 4. This fact will cause all kind of havoc if replication ever comes into being. I would recommend investigaing if it can be removed and doing so if at all possible.<div><br></div><div>As for the "flush logs" the behavior that depends upon the version of MySQL you are using. <a href="http://dev.mysql.com/doc/refman/<major>.<minor>/en/reset-master.html">http://dev.mysql.com/doc/refman/<major>.<minor>/en/flush.html</a> would be your best resource.</div><div><br></div><div><blockquote type="cite">What does "reset master" and "flush logs" do to a running database? At<br>no time does the script stop and restart the instances, BTW.<br></blockquote><div><br></div>I'm curious what your mysqldump command line looks like as well.</div><div><br></div><div>Best Regards,</div><div>Raymond</div></body></html>