mysql55: Default my.cnf extremely bare

Reported by m00dawg on 2011-02-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
IUS Community Project
Status tracked in El5-stable
El5-stable
Medium
BJ Dierkes

Bug Description

The default my.cnf is extremely bare:

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

This will force defaults and while the defaults have been improved in MySQL 5.5, it would be much better to have a more fleshed out config (such as the ones in use by Rackspace). Even if it states the obvious, it gives less savvy users a clue and makes it easier for experienced users to tweak things. The Rackspace my.cnf's have settings also not found in the standard my.cnf's included in the MySQL distribution (such as 'relay-log-space-limit', 'sql-mode', etc.).

Similarly, the my.cnf's included in /usr/share/doc/mysql55-server-5.5.8 are the ones MySQL provides. Which is fine (they suck) but it would be nice to have an IUS-centric config. As I recall previous IUS RPM distributions included a similar my.cnf to the Rackspace ones. I honestly thing the ones included with MySQL should be removed since they seem to be poorly maintained and also do not reflect modern server designs ('my-innodb-heavy-4G.cnf' being a good example).

BJ Dierkes (derks) on 2011-02-01
tags: removed: ius my.cnf mysql55
Changed in ius:
assignee: nobody → BJ Dierkes (derks)
BJ Dierkes (derks) on 2011-02-01
summary: - Default my.cnf extremely bare
+ mysql55: Default my.cnf extremely bare
Changed in ius:
status: New → Fix Committed
importance: Undecided → Medium
bharper (bharper) wrote :

Hey Sweetums,

I am doing a little house cleaning with old bugs. The my.cnf file for mysql55 has been updated a few this request. I am going to close out this bug.

-Ben

m00dawg (tim-moocowproductions) wrote :

Cool dawg. I haven't used the base my.cnf in a /long/ while so I lost track of this. I assume it's using the same my.cnf the DBA team made a while back (the one with the ASCII cows all over it)?

bharper (bharper) wrote :

The my.cnf file does still have the ASCII cows. The last commit was back on 07/31/2012.

m00dawg (tim-moocowproductions) wrote :

Happy pants dance time!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers