ourdelta-developers team mailing list archive

[Arjen Lentz <arjen@xxxxxxxxxxxxxxxx>]

Hi Erik

On 01/11/2008, at 3:52 AM, Erik Ljungstrom wrote:
> I can see the value of adding a patch like that, but that wouldn't as
> far as I can see (just had a very quick glance) work for command line
> supplied arguments. So maybe use two patches?


Euh you mean fed to the command line of mysqld_safe?
True, that. Did you have a look at mysqld_multi also?

By the way I did find where to tweak it in the my_print_default code  
(mysys library actually so it'll be in all tools), just turns out I  
need a new pointer variable to deal with things in the right spot. I  
was trying to do without but all existing vars are in use at that point.


Cheers,
Arjen.
-- 
Arjen Lentz, Director @ Open Query (http://openquery.com.au)
Training and Expertise for MySQL in Australia and New Zealand

OurDelta: free enhanced builds for MySQL @ http://ourdelta.org

-- 
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