[mythtv-users] Disabling MySQL binary logging ( log-bin ) (was Re: Disk space problem)

Michael T. Dean mtdean at thirdcontact.com
Tue Aug 4 18:16:42 UTC 2009


On 08/04/2009 02:01 PM, Mark Garland wrote:
> Hi Jim - that's good news that you've got to the bottom of your space hog.
>
> At the risk of hijacking your thread, I had a question relating to Mike's
> response to your question:
> I've checked my my.cnf, and can find no string matches of "log-bin" - so
> does that mean I am safe from my /var directory filling up?
>
> Mike said:
> "http://www.mythtv.org/docs/mythtv-HOWTO-6.html (Yes, I know that's the
> MySQL section.  Still, read it.  No, really.  Trust me.  Fine, at least read
> the first sentence.)"
>
> The sentence he refers to reads:
> "When you install MySQL 5.x you will also want to comment out "log-bin" in
> your my.cnf configuration file. This option will quickly fill your "/var"
> disk partition with many gigabytes of data, unless you are doing database
> replication and deleting these files regularly."
>
> P.S.  I'm newish to Linux, and new to Myth/MySQL, so basic comments welcome!

If your MySQL configuration file (and, specifically, the one that's used 
when mysqld is started--which means if there's a $HOME/.my.cnf in the 
environment of the user starting mysqld, you're not using 
/etc/{,mysql/}my.cnf) has no mention of log-bin, binary logging is disabled.

On any sane distro, you shouldn't see mysqld started from an environment 
with a HOME that causes a $HOME/.my.cnf to become visible, so you're 
probably OK.  Just watch to see if you're getting some fast-growing log 
files, or you can use SHOW BINARY LOGS; or SHOW MASTER STATUS; in the 
mysql command line client (as a mysql user with sufficient 
privileges--SUPER and/or REPLICATION CLIENT) to know for sure.

Mike


More information about the mythtv-users mailing list