Re: [gentoo-user] Should mysql crash sometimes?

[kashani]

On 11/29/2010 5:46 AM, Grant wrote:
>> You can add it to /etc/mysql/my.cnf and restart. Remove it and restart again
>> when you've finished.
>>
>> kashani
>
> That worked perfectly, thank you.
>
> I've run mysql_upgrade successfully and all of the warnings have
> disappeared from the mysql log file except the following:
>
> [Warning] No argument was provided to --log-bin, and --log-bin-index
> was not used; so replication may break when this MySQL server acts as
> a master and has his hostname changed!! Please use
> '--log-bin=mysqld-bin' to avoid this problem.
>
> Should I change the default 'log-bin' line in /etc/mysql/my.cnf to
> 'log-bin = mysqld-bin'?

If you're not replicating, you can ignore that error though what you've 
posted above should work. I forget what's in the default my.cnf these 
days, but you should also do the following.

Add this line to your /etc/mysql/my.cnf and it'll need to be in the 
[mysqld] section.

expire_logs_days = 7

Then log into Mysql and run this command to set the variable without 
having to restart Mysql.

SET GLOBAL expire_logs_days=7;

This will make sure that your logs expire and you don't fill up /var. If 
you're replicating you'll want to make sure that 7 days fits your needs.

kashani