Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 29211 - mysql warning
Summary: mysql warning
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Gentoo Linux MySQL bugs team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-20 12:29 UTC by Andrei Ivanov
Modified: 2004-02-29 14:17 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Ivanov 2003-09-20 12:29:30 UTC
I see this warning in mysqld.err:
Warning: Ignoring user change to 'mysql' because the user was set to 'mysql' 
earlier on the command line

It would be nice if it wouldn't show up... :)

mysql-4.0.15
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2003-10-02 14:07:56 UTC
I don't see why it is even creating the message.
The only user setting is "user = mysql" in /etc/mysql/my.cnf
it isn't set anywhere else!
Comment 2 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2003-11-14 18:39:57 UTC
verified as non-gentoo bug and sent upstream.
http://bugs.mysql.com/bug.php?id=1842
Comment 3 Sylvain Demers 2004-02-29 14:17:29 UTC
Well, from the mySQL bug site, I don't think they are going to do anything about it.

A little search revealed that the /usr/bin/mysqld_safe does indeed set the --user flag. The parse_arguments() function near the top does receive the user flag at some point, but I've not yet been able to figure out when exactly.

In several places in that script, it appear to say that the info is fetched from the my.cnf file. On line 106, the comment says: "Get first arguments from the my.cnf file, groups [mysqld] and [mysqld_safe]"

Additionally, line 96 (of mysqld_safe) is this:
	user=mysql

I've commented out the "user" line in my.cnf and the server starts fine, without the warning. Attempts to prevent mysqld_safe from setting the user resulted in mySQL not starting at all.