This is a discussion on "flush logs" vs. mysqladmin within the MySQL General forum forums, part of the MySQL category; --> We run a mysqladmin flush-logs from cron every night. This causes our server to start a new binary log. ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| We run a mysqladmin flush-logs from cron every night. This causes our server to start a new binary log. However, the slow query log does not get flushed - our server continues updating the same slow query log file. If I run mysql and then issue a "flush logs" command, it flushes the binary logs and the slow query log as well. - Redhat ES 4 - MySQL 5.0.24 from redhat-supplied RPM - Both mysqladmin from cron, and my mysql "flush logs", use -u root Why does mysqladmin not flush the slow query log? -- Cos |
| ||||
| At 12:12 PM -0400 6/12/07, Ofer Inbar wrote: >We run a mysqladmin flush-logs from cron every night. This causes our >server to start a new binary log. However, the slow query log does >not get flushed - our server continues updating the same slow query >log file. > >If I run mysql and then issue a "flush logs" command, it flushes the >binary logs and the slow query log as well. > > - Redhat ES 4 > - MySQL 5.0.24 from redhat-supplied RPM > - Both mysqladmin from cron, and my mysql "flush logs", use -u root > >Why does mysqladmin not flush the slow query log? It does, but the slow query log (just like the general query log) isn't created as a numbered sequence of files. You'll need to rotate it yourself. -- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com |