Summary: | dev-db/mysql-init-scripts - better support for multiple servers | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bernd Wurst <bugzilla-gentoo> |
Component: | New packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | hanno, walter |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bernd Wurst
2007-03-22 07:44:06 UTC
my own existing setups are: ln -s /etc/init.d/{mysql,mysql.slave} cp /etc/conf.d/{mysql,mysql.slave} and then I edit conf.d/mysql.slave. But I'll look at supporting some this for you. Yes, because MySQL is a basic service used as a component by many (web based and other) systems it would be very helpful to have multiple instances for testing, debugging, etc. An initial implementation requiring a single version for all instances would be fine, a better implementation would allow arbitrary use of any installed version for any desired instance. (This would be a great help for Gentoo-based developers, who could elegantly test code against different MySQL versions. Because historically major functionality in MySQL has been broken (eg: relatively long-leved table-specific GRANT bug!), it is not hard to see how useful this could be!) Just FYI the OpenVPN multiple init.d script was also my introduction to multiple instances of a given service, I found it extremely straightforward and currently use it on many machines, and have come to expect this from Gentoo init scripts. (I just voted on another bug to bring this to memcached.) It would be excellent to see this functionality brought to gentoo's MySQL init script. Implemented in new mysql-init-scripts-2.0_pre1 |