broken safe_mysqld --defaults-file

Hello, everyone:

safe_mysqld (tested in 4.0.12, I believe present in all other versions) will
insist on using its hard-coded datadir when --defaults-file option is given.
This results in a very counter-intuitive behaviour. One would expect
safe_mysqld to honor everything specified in the defaults file pointed to,
while in fact, the default hard-coded datadir ends up taking precedence.

Suggested fix:

If the argument defaults-file is present, and datadir is specified in the
defaults file, do not pass --datadir argument to mysqld inside safe_mysqld .

--
Sasha Pachev
Create online surveys at http://www.surveypro.com/

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org
Sasha Pachev [ Do, 24 April 2003 03:06 ] [ ID #67689 ]
Datenbanken » gmane.comp.db.mysql.bugs » broken safe_mysqld --defaults-file

Vorheriges Thema: broken safe_mysqld --defaults-file
Nächstes Thema: RE: Problem with "load data infile..." on 3.23.52 for Windows 2000