Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#19075 - [mysql] initscript defeats custom database location
Attached to Project:
Arch Linux
Opened by Nicklas Overgaard (nicklas) - Tuesday, 13 April 2010, 09:00 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 13 April 2010, 10:47 GMT
Opened by Nicklas Overgaard (nicklas) - Tuesday, 13 April 2010, 09:00 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 13 April 2010, 10:47 GMT
|
DetailsDescription:
In MySQL, if you want to have your databases located in another directory than "/var/lib/mysql" you can change the datadir in my.cnf. However, the rc.d iniscript for mysqld, executes "mysqld_safe --datadir=$MYSQLD_ROOT" where $MYSQLD_ROOT is the default directory. This actually overrides the definitions made in the my.cnf file, making it impossible to move the directory. I had changed the script on a production mysql server (removed the --datadir directive), but with the most recent update of mysql, pacman relentlessly replaced the rc.d file - leaving MySQL unable to start (!) I have attached a patch for the rc.d file, which you can apply to fix the issue. Additional info: Version: mysql 5.1.45-1 It was during (or should i say after) the update from the previous version (i don't remember the version number) to the above, that the problem occurred. Steps to reproduce: * Stop mysql * Change the "datadir" in my.cnf to something else than the default * move your datadir directory to the new location. * Make sure that it is properly owned by mysql * Try to start mysql.. it will now fail. Now apply the patch to the rc.d file and try again. MySql should start correctly now. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Tuesday, 13 April 2010, 10:47 GMT
Reason for closing: Implemented
Additional comments about closing: see comments
Tuesday, 13 April 2010, 10:47 GMT
Reason for closing: Implemented
Additional comments about closing: see comments
mysqld.patch
However, would'nt it be more clean to actually define this in the my.cnf file? And then just enter the default value which is used now?
I committed on trunk a new mysqld that does not need conf.d/mysql