FS#4096 - my.cnf innodb confusion

Attached to Project: Arch Linux
Opened by Moo-Crumpus (Moo-Crumpus) - Friday, 03 March 2006, 15:19 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

If mysql shoudl use InnoDB tables, starting the daemon fails due to wrong preconfiguration in my.cnf.

mysqld will create folders and permissions for $MYSQLD_ROOT = "/var/lib/mysql".
my.cnf sets the datadir properly to /var/lib/mysql.
Otherwise, the innodb part in my.cnf tells innodb to store data in /usr/var - which is not prepared by the daemon: Mysqld fails to start. It would be straight to use /var/lib/mysql for InnoDB as well. This can simply be done by changing the preconfigured InnoDB-settings in my.cnf from:

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /usr/var
innodb_data_file_path = /usr/var
innodb_log_group_home_dir = /usr/var
innodb_log_arch_dir = /usr/var

to

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /var/lib/mysql
innodb_data_file_path = /var/lib/mysql
innodb_log_group_home_dir = /var/lib/mysql
innodb_log_arch_dir = /var/lib/mysql

It would be nice if you would change the my.cnf used by the mysql-package, and in this case a user really has just to "uncomment" those lines.

With kind regards

Ingo Huber
This task depends upon

Closed by  Judd Vinet (judd)
Friday, 03 March 2006, 23:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed for next mysql build.

Loading...