Do we have a place like the launchpad Blueprints where we could start working up ideas for this? Or should I just file a bug/use this one as a place to collect thoughts?
Monty sean finney wrote: > severity 435165 wishlist > thanks > > hi dan, > > yes, i've actually been talking with on of the "debian guys" within mysql > about how this is a fairly common problem in real-world installations for > them as well. not only multiple instances, but multiple versions as well. > i'll probably be talking with him more about the details of implementing > this, but i'm sure the patch below would be a good first step since we'll > have to do this abstraction at some point anyway. > > for a final version, i think we'll probably do something similar to what > pitti > set up with the postgres packages, but i'm also not familiar enough with that > to know all the details of the implementation. > > i'll take a look at the specifics of the patch the next time i'm sitting down > with the packaging, and maybe we can use this BR for general discussion about > this topic both in the meantime and until we get the full support. > > > thanks, > sean > > On Sunday 29 July 2007 09:24:46 pm Dan Munckton wrote: >> Package: mysql-server-5.0 >> Version: 5.0.45-1 >> Severity: minor >> >> This is the result of the bug reported in Ubuntu. Raised here to pass >> the debdiff upstream to Debian. >> >> https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.0/+bug/106244 >> >> A user reported that they were trying to run multiple instances of >> mysqld by duplicating the init script and changing the value of the CONF >> variable within it to point to another configuration file. They raised >> the bug in Ubuntu because the /etc/mysql/my.cnf is hard coded in a lot >> of the startup scripts, and prevented them from easily running >> multi-instances in this way. >> >> After some analysis and discussion with mathiaz and infinity from the >> ubuntu-server team it was agreed that we cannot properly support >> multi-instances in this way because the maintainer scripts are not >> designed to deal with this situation and could therefore lead to >> problems on package upgrade/removal. Instead the proper way to do things >> would seem to be to use mysqld_multi. >> >> A patch has been prepared which clearly comments the CONF variable >> stating that multi-instances are not supported in this way, and removes >> some of the hard-coded instances of '/etc/mysql/my.cnf' for the sake of >> tidyness. >> >> (This is my first bug report to the Debian BTS sorry if there are any >> slip-ups). >> >> >> -- System Information: >> Debian Release: 4.0 >> APT prefers feisty-updates >> APT policy: (500, 'feisty-updates'), (500, 'feisty-security'), (500, >> 'feisty-backports'), (500, 'feisty') Architecture: i386 (i686) >> Shell: /bin/sh linked to /bin/dash >> Kernel: Linux 2.6.20-16-generic >> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> pkg-mysql-maint mailing list >> [EMAIL PROTECTED] >> http://lists.alioth.debian.org/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
