Re: [Devil-Linux-discuss] mysql on 1.6.0-RC2 and newer

[Dominic R. <dl...@ed...>]

On 15/03/2012 13:21, Heiko Zuerker wrote:
> Quoting Dominic Raferd<dl...@ed...>:
>
>> On 15/03/2012 13:03, Heiko Zuerker wrote:
>>> Hey,
>>>
>>> is anybody using 1.6.0-RC2 (or the current CVS version) together with mysql?
>> yes (1.6.0-RC2-server x86)
>>
>>> If yes, is your mysql server starting on boot?
>> yes, but I had to run mysql_upgrade (try: man mysql_upgrade)...
> I did that.
> I get the following error in the mysql.err file:
> -----------------------------------------
> 120315 08:18:15 mysqld_safe mysqld from pid file /var/run/mysql.pid ended
> 120315 08:18:57 mysqld_safe Starting mysqld daemon with databases from
> /var/mysql
> 120315  8:18:58 [ERROR] Fatal error: Please read "Security" section of
> the manual to find out how to run mysqld as root!
>
> 120315  8:18:58 [ERROR] Aborting
> -----------------------------------------
>
> When I start it on the command line via the init script, then it works
> fine and runs under the  mysql user.
>
> I have this specified in the config file:
> MYSQL_PARM="--user=mysql --pid-file=/var/run/mysql.pid --datadir=/var/mysql"
>

Hmm, it works for me. I have:
MYSQL_PARM="--user=mysql --pid-file=/var/run/mysql.pid 
--datadir=/home/mysql --tmpdir=/home/bigtmp"

So I guess in your case, but not mine, mysqld_safe is not picking up 
$MYSQL_PARM correctly? Has there been a change in CVS to 
/etc/init.d/mysqld or to /usr/bin/mysqld_safe?