[mythtv-users] /var/lib/mysql filled /var partition - how to clean up?

[Chris Moewes-Bystrom]

Unless you are dloing replication there isn't any need to have the bin
log enabled.

Look for the option "log-bin" in your my.cnf file (typically in /etc
or in /var/lib/mysql).

If for some reason you want to have bin logging on, you can set the
"max_binlog_size" option. This will force mysqld to rotate to a new
log when it reaches your setting. It is safe to delete all but the
largest numbered binlog without shutting down the server, unless you
are doing replication, in which case you want to make sure that any
slave DBs are using the latest binlong before deleting the others.



On 10/7/06, Brad DerManouelian <myth at dermanouelian.com> wrote:
> On Oct 7, 2006, at 9:15 PM, catfish wrote:
>
> > Mark Knecht wrote:
> >>    As the title indicates my Myth server's /var partition was filled
> >> up today when a number of 'dragonfly-bin.xxxxxxx files in
> >> /var/lib/mysql got too big. This caused mythfrontend to not run at
> >> all.
> >
> >
> > This appears to be Mysql binary log files, you can read about it here:
> > http://dev.mysql.com/doc/refman/5.0/en/binary-log.html
> > It keeps track of changes made to the database, and mythtv can make
> > lots
> > of changes. I assume it would be best to disable the logging.
>
> Actually, I believe *best* would be to rotate your logs so you get
> the latest, most relevant ones just in case something goes awry.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>


-- 
Christopher Moewes-Bystrom
www.moewes.com
chris.moewes at gmail.com