On Sun, 10 Aug 2003 13:10:30 -0400 (EDT) Matthew Saltzman <[EMAIL PROTECTED]> wrote:
> The /etc/logrotate.d/mysqld script in mysql-server-3.23.56-1.72 invokes > "mysqladmin flushlogs" in the prerotate and postrotate sections. If mysql > has a root password, then these steps fail. It is possible to give the > mysql root password on the command line, but /etc/logrotate.d/mysqld is > world readable. > > This bug is reported in Bugzilla 58035 as fixed in 3.23.47-4, but it's > obviously not in 3.23.56-1.72. Strangely, in 3.23.56-1.80, mysqld is > killed with signal HUP, but this is apparently not ideal either, according > to a comment in the Bugzilla report. > > Can the protections on /etc/logrotate.d/mysqld be changed without breaking > something, or is the kill the best solution? Any idea why the .72 and .80 > versions are different? > > -- > Matthew Saltzman > Hey Matthew, The newer RedHat rpm solves the issue. From everything i've seen there just isn't a problem using HUP to flush the logs. You can ignore the FUD and just upgrade to the new RPM. Cheers, Sean P.S. Note there is some discussion of this issue at: http://www.geocrawler.com/mail/thread.php3?subject=Lost+bin-log%28s%29+following+logrotate+affecting+recovery%2C&list=8 However, the poster who is worried here is mixing a couple of problems together including the rotation of binary logs which RedHat doesn't do. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
