ius-coredev team mailing list archive

[m00dawg <tim@xxxxxxxxxxxxxxxxxxxxx>]

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)?

-- 
You received this bug notification because you are a member of IUS Core
Development, which is subscribed to IUS Community Project.
https://bugs.launchpad.net/bugs/711271

Title:
  mysql55: Default my.cnf extremely bare

Status in IUS Community Project:
  Fix Released
Status in IUS Community Project el5-stable series:
  Fix Released

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).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ius/+bug/711271/+subscriptions