[Bug 353120] New: multi mysql server support in rcmysql
https://bugzilla.novell.com/show_bug.cgi?id=353120 Summary: multi mysql server support in rcmysql Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: richard.bos@xs4all.nl QAContact: qa@suse.de Found By: Customer Would it be possible to extend (/usr/bin/)rcmysql a bit so, it supports the start up of multiple mysql servers on a system? A played around a bit with this and changed some lines in a copy of rcmysql to get this accomplished. Please find below a diff of the 2 files (the original rcmysql and my hacked version): # diff -u /usr/sbin/rcmysql /var/tmp/rcmysql2 --- /usr/sbin/rcmysql 2007-09-22 03:31:58.000000000 +0200 +++ /var/tmp/rcmysql2 2008-01-10 16:00:20.000000000 +0100 @@ -17,7 +17,7 @@ # Default-Stop: # Description: Start the MySQL database server ### END INIT INFO - +set -x # Shell functions sourced from /etc/rc.status: # rc_check check and set local and overall rc status # rc_status check and set local and overall rc status @@ -69,12 +69,14 @@ # the original MySQL init script # Note: If you want to change these variables, you'll make your life easier # if you do so in /etc/my.cnf, which is preserved during upgrades +SERVER_GNR=2 + basedir=/usr -datadir=/var/lib/mysql +datadir=/var/lib/mysql$SERVER_GNR mysql_daemon_user=mysql mysql_daemon_group=mysql -pid_file=/var/lib/mysql/mysqld.pid -socket=/var/lib/mysql/mysql.sock +pid_file=/var/lib/mysql$SERVER_GNR/mysqld.pid +socket=/var/lib/mysql$SERVER_GNR/mysql.sock print_defaults=/usr/bin/my_print_defaults mode=$1 # start or stop @@ -82,10 +84,12 @@ parse_arguments() { for arg do case "$arg" in - --basedir=*) basedir=`echo "$arg" | sed -e 's/^[^=]*=//'` ;; - --datadir=*) datadir=`echo "$arg" | sed -e 's/^[^=]*=//'` ;; - --pid-file=*) pid_file=`echo "$arg" | sed -e 's/^[^=]*=//'` ;; - --socket=*) socket=`echo "$arg" | sed -e 's/^[^=]*=//'` ;; + --basedir=*) basedir=`echo "$arg" | sed 's/^[^=]*=//'` ;; + --datadir=*) datadir=`echo "$arg" | sed 's/^[^=]*=//'` ;; + --pid-file=*) pid_file=`echo "$arg" | sed s/^[^=]*=//'` ;; + --socket=*) socket=`echo "$arg" | sed s/^[^=]*=//'` ;; + --port=*) port=`echo "$arg" | sed 's/^[^=]*=//'` ;; + --log=*) log=`echo "$arg" | sed 's/^[^=]*=//'` ;; esac done } @@ -131,7 +135,7 @@ return 1 } -parse_arguments `$print_defaults $defaults mysqld mysql_server` +parse_arguments `$print_defaults $defaults mysqld$SERVER_GNR` export TMPDIR=$datadir/.tmp if ! test -d "$TMPDIR"; then mkdir "$TMPDIR" @@ -147,8 +151,8 @@ case "$1" in start) # exit gracefully, if we are already running - checkproc $MYSQLD && echo -n "Starting service MySQL " && \ - rc_status -v && rc_exit + # checkproc $MYSQLD && echo -n "Starting service MySQL " && \ + # rc_status -v && rc_exit # Test, if safe_mysqld actually exists SAFE_MYSQLD=/usr/bin/mysqld_safe @@ -160,7 +164,7 @@ if test "$MYSQLD_DEBUG" = yes; then # add --log, --core-file and --debug # but only if not already set in my.cnf - if ! $print_defaults mysqld | \ + if ! $print_defaults mysqld$SERVER_GNR | \ grep -q -e '--log$' -e '--log[[:blank:]=]' then debug_flags="--log=$datadir/mysqld-query.log" @@ -256,8 +260,10 @@ $SAFE_MYSQLD \ --mysqld=${MYSQLD#/usr/sbin/} \ $debug_flags \ + --port=$port \ --user=$mysql_daemon_user \ --pid-file=$pid_file \ + --log=$log \ --socket=$socket \ --datadir=$datadir &>/dev/null & This diff does not result in an rcmysql script that supports multiple mysql servers (at least not on my system, but it is close), but it gives I think an idea of what is to be changed to get rcmysql ready to support multiple mysql server. (The changes up to line 82 are actually not needed I think, as those are set in /etc/my.cnf). I did not touch the code that support upgrading of a database to a newer version. Perhaps that "--log" is not correct and that the argument should actually be --err-log, but I could not find it what the argument should be. If this feature request is honored it would be nice, if the file /etc/my.cnf would have an example of an additional mysqld instance (but commented out e.g.) # [mysqld2] # port = 3307 # datadir = /var/lib/mysql2 # socket = /var/lib/mysql2/mysql.sock # pid-file = /var/lib/mysql2/mysqld.pid # log = /var/lib/mysql2/mysqld.log Another problem is the client as that has the default settings: [client] port = 3306 socket = /var/lib/mysql/mysql.sock For the 2nd (or more) instance the client should look e.g. at: [client] port = 3307 socket = /var/lib/mysql2/mysql.sock Anyway, support for multiple mysql servers out of the opensuse box would be awesome and would save users a lot of time when done correctly! Thanks in advance for looking into this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c1
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c2
Richard Bos
But your version only starts the second version, right?
That's correct, but I first needed to check whether supporting multiple mysql servers on 1 system would be an option for openSUSE. Appearantly it is :)
What would be more reasonable would be an /etc/sysconfig/mysql, where one could set which server(s) they want to start. Could you try that?
What about just checking the /etc/my.cnf file with e.g.: # grep "^\[mysqld[0-9]*\]" /etc/my.cnf [mysqld] [mysqld2] Would this work? Please change the bug status to needinfo, after answering the question. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c3
Michal Marek
But your version only starts the second version, right?
That's correct, but I first needed to check whether supporting multiple mysql servers on 1 system would be an option for openSUSE. Appearantly it is :)
Well, I'm not opposed to the idea per se :)
What would be more reasonable would be an /etc/sysconfig/mysql, where one could set which server(s) they want to start. Could you try that?
What about just checking the /etc/my.cnf file with e.g.: # grep "^\[mysqld[0-9]*\]" /etc/my.cnf [mysqld] [mysqld2]
Would this work?
If you limit it to numbers, maybe. If you want to support more fancy names, then you have to make sure you don't start the [mysqldump] "server" ;). I still think that an explicit listing of configuration(s) you want to use would be useful, it would also allow you to temporarily disable some. And important: you also need to make mysqld_safe and the mysqld server aware of which section of the config it has to use! Also, currently the rc script exctracts options from [mysqld] and (optionally) [mysql_server] and merges them, what to do if there's [mysqld], [mysqld2] and [mysql_server]? As it's getting more complicated, I'd suggest to ask on the mysql packagers list (http://lists.mysql.com/packagers) what other packagers and mysql developers think about this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c4
--- Comment #4 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c5
--- Comment #5 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c6
--- Comment #6 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c7
--- Comment #7 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c8
--- Comment #8 from Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c9
--- Comment #9 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c10
--- Comment #10 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c11
Michal Marek
Created an attachment (id=190375) --> (https://bugzilla.novell.com/attachment.cgi?id=190375) [details] Another version of /etc/init.d/mysql
I think your latest proposal still has the problem that all the mysqld instances will look into the '[mysqld]' section for options not passed on the command-line. This means that only those options handled by parse_arguments can be set per-server afaics. Correct me if I'm wrong.
Start all databases defined in /etc/sysconfig/mysql and that have been configured in /etc/my.cnf (normal usage during boot process): # rcmysql start
Start a (1 or more) databasefrom the command line (probably used for testing) # rcmysql start mysqld2 (... mysqldN)
Hmm, interesting :)
BTW: more information about multiple mysql servers can be found at: http://dev.mysql.com/doc/refman/5.0/en/multiple-servers.html http://dev.mysql.com/doc/refman/5.0/en/mysqld-multi.html
Thanks for the links! I didn't know that there are actually scripts for that as part of the mysql distribution. Do you think we could utilize mysqld_multi or mysqlmanager from within rcmysql? I've been thinking about using mysqlmanager in the 5.1 rpms already (without having multiple servers in mind). I think it could solve the problem of not being able to override arbitrary options in the [mysqldN] section. BTW, if you want, I can give you access to the server:database:mysql51 project to try out this feature. If it turns out to be working, I can merge it to the Factory mysql package. (In reply to comment #9 from Richard Bos)
comment #8: okay, that's understandable. What about adding an directory that can be used to store all the other (additional to mysql) databases.
The mysql rpm could e.g just provide /var/lib/mysqldb/ with a README stating its purpose. Would that be doable?
Sure, something like that is possible. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c12
--- Comment #12 from Richard Bos
I think your latest proposal still has the problem that all the mysqld instances will look into the '[mysqld]' section for options not passed on the command-line. This means that only those options handled by parse_arguments can be set per-server afaics. Correct me if I'm wrong.
I think I have to correct you here. If the output of my_print_defaults can be trusted than each database section is a section on its own. For example: # my_print_defaults mysqld | sort -u --datadir=/var/lib/mysql --key_buffer=16M --log=/var/lib/mysql/mysqld.log --max_allowed_packet=1M --myisam_sort_buffer_size=8M --net_buffer_length=8K --pid-file=/var/lib/mysql/mysqld.pid --port=3306 --read_buffer_size=256K --read_rnd_buffer_size=512K --server-id=1 --skip-locking --socket=/var/lib/mysql/mysql.sock --sort_buffer_size=512K --table_cache=64 But: # my_print_defaults mysqld2 | sort -u --datadir=/var/lib/mysql2 --log=/var/lib/mysql2/mysqld.log --pid-file=/var/lib/mysql2/mysqld.pid --port=3307 --socket=/var/lib/mysql2/mysql.sock You probable know the settings of [mysqld], my [mysqld2] is: [mysqld2] port = 3307 datadir = /var/lib/mysql2 socket = /var/lib/mysql2/mysql.sock pid-file = /var/lib/mysql2/mysqld.pid log = /var/lib/mysql2/mysqld.log
BTW: more information about multiple mysql servers can be found at: http://dev.mysql.com/doc/refman/5.0/en/multiple-servers.html http://dev.mysql.com/doc/refman/5.0/en/mysqld-multi.html
Thanks for the links! I didn't know that there are actually scripts for that as part of the mysql distribution. Do you think we could utilize mysqld_multi or mysqlmanager from within rcmysql? I've been thinking about using mysqlmanager in the 5.1 rpms already (without having multiple servers in mind). I think it could solve the problem of not being able to override arbitrary options in the [mysqldN] section.
I assume it is indeed possible, however as I have no further expertise of mysql it is really an assumption! My goal with this bug report is get multiple databases support working, with at least changes as possible. Once it works, further optimatizations can be added to the /etc/init.d/mysql script.
BTW, if you want, I can give you access to the server:database:mysql51 project to try out this feature. If it turns out to be working, I can merge it to the Factory mysql package.
How would you track what changes I make to the script? The BS does not have a commit notification AFAIK. I rather sent you the changes for review and that you commit to the BS. I can check out server:database:mysql51 and provide patches against the version in the BS. (In the meantime I checked out that repository)...
(In reply to comment #9 from Richard Bos)
comment #8: okay, that's understandable. What about adding an directory that can be used to store all the other (additional to mysql) databases.
The mysql rpm could e.g just provide /var/lib/mysqldb/ with a README stating its purpose. Would that be doable?
Sure, something like that is possible.
Will you add /var/lib/databases to the spec file? What about the current version of the init.d/mysql script. Is that okay with you? Should I continue working in the current direction? I have a small change (around 10 lines + a update to /etc/my.cnf) on my disk that I would like to provide to you. But it would be nice to get confirmation that I'm (we're) heading in the right direction. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c13
--- Comment #13 from Michal Marek
I think your latest proposal still has the problem that all the mysqld instances will look into the '[mysqld]' section for options not passed on the command-line. This means that only those options handled by parse_arguments can be set per-server afaics. Correct me if I'm wrong.
I think I have to correct you here. If the output of my_print_defaults can be trusted than each database section is a section on its own. For example:
That's unfortunately not sufficient. Consider this setting: [mysqld2] skip-networking datadir = /var/lib/mysql2 socket = /var/lib/mysql2/mysql.sock pid-file = /var/lib/mysql2/mysqld.pid log = /var/lib/mysql2/mysqld.log Then: # ./rcmysql2 start Starting mysql server: mysqld done Starting mysql server: mysqld done Starting mysql server: mysqld2 warning: /var/lib/mysql2/mysql.sock didn't appear within 30 seconds done That's because --skip-networking isn't propagated down to mysqld itself, which reads the default [mysqld] section and tries to bind to the already occupied tcp port 3306. IOW only arguments that are handled specially in parse_arguments can be set per-server. That's why I think using mysql_multi or mysqlmanager would be a solution. rcmysql would then only need to handle arguments it needs to know about (datadir, pid-file and socket). BTW, ./rcmysql2 stop seems to only shutdown the first instance.
BTW, if you want, I can give you access to the server:database:mysql51 project to try out this feature. If it turns out to be working, I can merge it to the Factory mysql package.
How would you track what changes I make to the script? The BS does not have a commit notification AFAIK.
An email when you make important changes will suffice (sure, commit notification in the bs would be cool). But what I wanted to say is that it would be better to first try this out in the buildservice and merge it to the distro after it has got some testing. The :mysql51 project is still rather experimental, so it's not such a big issue if something breaks there :) Factory mysql 5.0 is linked to server:database which is used more people, who don't expect it to break too often. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c14
Richard Bos
(In reply to comment #12 from Richard Bos)
I think your latest proposal still has the problem that all the mysqld instances will look into the '[mysqld]' section for options not passed on the command-line. This means that only those options handled by parse_arguments can be set per-server afaics. Correct me if I'm wrong.
I think I have to correct you here. If the output of my_print_defaults can be trusted than each database section is a section on its own. For example:
That's unfortunately not sufficient. Consider this setting:
[mysqld2] skip-networking datadir = /var/lib/mysql2 socket = /var/lib/mysql2/mysql.sock pid-file = /var/lib/mysql2/mysqld.pid log = /var/lib/mysql2/mysqld.log
Then:
# ./rcmysql2 start Starting mysql server: mysqld done Starting mysql server: mysqld done Starting mysql server: mysqld2 warning: /var/lib/mysql2/mysql.sock didn't appear within 30 seconds done
That's because --skip-networking isn't propagated down to mysqld itself, which reads the default [mysqld] section and tries to bind to the already occupied tcp port 3306. IOW only arguments that are handled specially in parse_arguments can be set per-server. That's why I think using mysql_multi or mysqlmanager would be a solution. rcmysql would then only need to handle arguments it needs to know about (datadir, pid-file and socket).
Okay, so than we need to decide on which one to use. Browsing there respective manual pages: http://dev.mysql.com/doc/refman/5.1/en/mysqld-multi.html http://dev.mysql.com/doc/refman/5.1/en/instance-manager-configuration-files.... I seem to prefer the mysqld-multi.html. It feels somehow more familair, than the manager one. Is it okay to choose / use mysqld-multi?
BTW, ./rcmysql2 stop seems to only shutdown the first instance.
That's correct and on purpose. I don't want to waste writing the stop (and the status) part of the code without knowing whether the start is okay or not. Which was a good decision, as you actually prefer to have another start part....
BTW, if you want, I can give you access to the server:database:mysql51 project to try out this feature. If it turns out to be working, I can merge it to the Factory mysql package.
How would you track what changes I make to the script? The BS does not have a commit notification AFAIK.
An email when you make important changes will suffice (sure, commit notification in the bs would be cool). But what I wanted to say is that it would be better to first try this out in the buildservice and merge it to the distro after it has got some testing. The :mysql51 project is still rather experimental, so it's not such a big issue if something breaks there :) Factory mysql 5.0 is linked to server:database which is used more people, who don't expect it to break too often.
Is it possible to revert to a certain revision in the buildserver? I don't remember if something like "osc co -r rXX" is possible. But than again how would one know the what has changed, without real log messages... For archiving purposes: packages/osc/server:database:mysql51/mysql> osc up osc At revision 24. Would be nice (and very handy) if you would let me know for the weekend what your thought are! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c15
--- Comment #15 from Michal Marek
Okay, so than we need to decide on which one to use. Browsing there respective manual pages: http://dev.mysql.com/doc/refman/5.1/en/mysqld-multi.html http://dev.mysql.com/doc/refman/5.1/en/instance-manager-configuration-files....
I seem to prefer the mysqld-multi.html. It feels somehow more familair, than the manager one. Is it okay to choose / use mysqld-multi?
OK, let's go for mysqld-multi then.
BTW, ./rcmysql2 stop seems to only shutdown the first instance.
That's correct and on purpose. I don't want to waste writing the stop (and the status) part of the code without knowing whether the start is okay or not.
I see, no problem.
Is it possible to revert to a certain revision in the buildserver? I don't remember if something like "osc co -r rXX" is possible. But than again how would one know the what has changed, without real log messages...
Yes, the buildservice stores all revisions of the package sources and recent osc has some support for it (e.g. osc co -rXX is possible). It's also possible to attach a log message to a commit (osc ci -m ...), but usually a note in the *.changes file is sufficient (and better IMO, because it's visible in the package changelog). I added you (your login is 'rbos', right?) to server:database:mysql51/mysql, feel free to apply your changes there. And don't worry about accidentally breaking this package. I'll watch the changes and test/correct/argue as needed ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c16
--- Comment #16 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c17
--- Comment #17 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c18
--- Comment #18 from Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c19
--- Comment #19 from Richard Bos
I think it's good as a starting point, provided you're going to work on the two FIXME's ;-) It would be nice if the database was automatically created and updated in both modes (the update is not needed urgently, though).
Done. See attached patch. It's not complete, as /etc/init.d/mysql has not been update to reflect the changes in this patch. But I assume that you understand what needs to be done.
Regarding /etc/my.cnf: We could add example sections, I'd probably prefer adding them as comments
That's fine with me.
(or adding a [mysqld1] that behaves the same as [mysqld], so that switching to mysqld_multi initially doesn't change anything).
We can do this, but only when this section is commented out and accompanied with a strong comment that informs the user about the following possible problem when mysqld1 is started; - the regular way of starting mysql should not be used anymore at all. Because that will result in 2 server processes that use the database files. This may corrupt the database!
But: then the config has to be marked as %config(noreplace), so that it doesn't get installed if the user changed his copy.
That's fine with me, strange that this is not already the case ;)
(Also, when we touch the config, it's probably good time to get rid of --err-log and replace it with --log-error, because --err-log doesn't exist since 5.0).
I leave that up to you.
Then we need the sysconfig file, check http://en.opensuse.org/SUSE_Package_Conventions/Sysconfig how to deal with sysconfig files.
Okay.
Thanks for working on this feature so far!
Hopefully, it is now enough ready to start including it in the openSUSE distro (I'll do some more fine tuning, so it will be easier to integrate it). Let me know your thoughts. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c20
--- Comment #20 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c21
--- Comment #21 from Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c22
--- Comment #22 from Richard Bos
Michal,
Op Wednesday 13 February 2008 09:28:30 schreef bugzilla_noreply@novell.com:
--- Comment #21 from Michal Marek
2008-02-13 01:28:29 MST --- Thanks! Could you send a short mail about this feature to opensuse-factory@ and/or opensuse@ to invite people to test it a bit? https://bugzilla.novell.com/show_bug.cgi?id=353120
Did this and how now further? Would it possible to include the patch in 11.0-alpha3 that is scheduled to be released mid March?
Either alpha3 or beta1. But it should go in. Michal RB: hopefully it will be alpha3, as that gives more time for testing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c23
--- Comment #23 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c24
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c25
--- Comment #25 from Richard Bos
How come? Did I do something wrong? This is mysql-5.1.23-14 from the :mysql51 project (I updated it to 5.1.23 yesterday).
To what do you refer with "How come?"? Do you mean the double mysql processes? I believe that those are created by mysqld_safe (that's what mysqld_multi executes). So, I expect multiple processes for 1 database, however I would think that it should be 1 mysqld_safe and 1 mysqld process. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c26
--- Comment #26 from Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c27
--- Comment #27 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c28
--- Comment #28 from Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c29
--- Comment #29 from Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c30
--- Comment #30 from Richard Bos
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c31
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c32
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=353120
User richard.bos@xs4all.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c33
--- Comment #33 from Richard Bos
The feature is there.
Hopefully Stephan Kulow (as release coordinator) will make some noise about this feature. It's a good one to distinqish from other linux distro's ;)
Thanks for working on this. Thank you too, it was nice to work with you on this issue!
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=353120
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c34
--- Comment #34 from Michal Marek
Hopefully Stephan Kulow (as release coordinator) will make some noise about this feature. It's a good one to distinqish from other linux distro's ;)
You can a) tell him so, or b) make noise about it yourself. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com