ourdelta-developers team mailing list archive
-
ourdelta-developers team
-
Mailing list archive
-
Message #00122
[Bug 290190] Re: mysqld_safe does not honour underscores in options like mysqld does
Hi,
> True, that. Did you have a look at mysqld_multi also?
mysqld_multi doesn't take arguments that's affected by this, and quite
happily passes anything on to mysqld.
> By the way I did find where to tweak it in the my_print_default code
I'm not sure if anything is actually required in my_print_defaults. Anything coming from there as far as mysqld_safe is concerned goes through parse_arguments() and will be fixed by the patch anyways. What other tools do you have in mind?
We would still need the mysqld_safe patch since command line arguments are separate from anything to do with my_print_defaults
Thanks,
Erik
--
mysqld_safe does not honour underscores in options like mysqld does
https://bugs.launchpad.net/bugs/290190
You received this bug notification because you are a member of OurDelta-
developers, which is the registrant for OurDelta.
Status in OurDelta - Builds for MySQL: Confirmed
Bug description:
mysqld accepts both dashes and underscores in server options, however mysqld_safe does not.
Since it's unclear from the user's perspective (and they shouldn't NEED to know!) which options get processed only by mysqld_safe, this can mean that they use an option in the wrong way but don't notice it.
Example... open_files_limit
When written like that, it mysqld_safe will not recognise it and thus not call ulimit -n
...
The option WILL be feed to mysqld so it shows the "correct" number in SHOW GLOBAL VARIABLES. Except, since ulimit wasn't called, it's not actually in effect!
See http://bugs.mysql.com/40368
References