On Sun, Oct 21, 2001 at 05:59:47PM -0700, Jesse Thompson wrote:
>
> Something that is not entirely clear about the mysql binary logs in
> the documentation is whether the mysql daemon itself begins to write
> logs with different names at different points in time, or if it
> simply writes to .001 and your logrotate daemon (perhaps as directed
> by mysql's bundled logrotate scripts) rotates out old files at
> intervals.
The binlog can be rotated for several reasons:
(1) You hit the maximum size for a binlog file (max_binlog_size), as
documented here:
http://www.mysql.com/doc/S/H/SHOW_VARIABLES.html
(2) You restart the server.
(3) You run FLUSH LOGS.
http://www.mysql.com/doc/F/L/FLUSH.html
(4) You send mysqld a SIGHUP.
http://www.mysql.com/doc/F/L/FLUSH.html
There are probably others I haven't thought of yet.
Jeremy
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936
MySQL 3.23.41-max: up 46 days, processed 1,001,714,194 queries (251/sec. avg)
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
