MySQL Bugs: #4265: icc build will not su to mysql user when starting

Bug #4265	icc build will not su to mysql user when starting
Submitted:	23 Jun 2004 23:30	Modified:	5 Aug 2004 15:43
Reporter:	Matthew Lord	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4,0.20	OS:	x86 linux
Assigned to:		CPU Architecture:	Any

Description:
I've noticed lots of oddities with the icc build on my RH 9 machine.  Another one is that I cannot start 
up the server with mysql.server or mysqld_multi because it acts like the user doesn't exist.  The user 
definitely exists as I'm using mysqld_multi with 4 other versions.

Here is the error:

Starting MySQL servers
Fatal error: Can't change to run as user 'mysql' ;  Please check that the user exists!
040623 17:13:57  Aborting

I also noticed that you have to use --force with mysql_install_db as well as resolveip doesn't seem to be 
working correctly. 

How to repeat:
Install mysql-standard-4.0.20-pc-linux-i686-icc

run ./scripts/mysql_install_db to see that problem.

cp support-files/mysql.server to /etc/ and try to start up mysql with
/etc/mysql.server start.

I've managed to workaround the startup problem by hand on Linux (RH 9). I assume that you've symlinked ou copied the '/usr/local/mysql-VERSION/support-files/mysql.server' to '/etc/init.d/mysql'. I assume, also, that you have an user named 'mysql' in your system.

su -c "/etc/init.d/mysql start' mysql

Duplicate of http://bugs.mysql.com/4408
The fact that resolveip is also affected can be explained: see those warnings when compiling:
mysqld.o(.text+0x1193):/home/mysql_src/mysql-4.0/sql/mysqld.cc:1045: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
<cut>
/home/mysql_src/mysql-4.0/sql/mysqld.cc:4893: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

icc is not responsible for that. The same happens when we test a binary built with gcc on the same machine. It's apparently a question of glibc incompatibility, and we have no fix yet.