Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On launching my CentOS VPS (setup by someone else), MySQL starts two processes on boot:

  1. mysql : /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql
  2. root: /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.

Is this normal / the correct way to setup MySQL (that root is running mysqld_safe?)


share|improve this question
all the parameters like key_buffer_size need to be on mysqld or mysqld_safe? – Artur Sonnenhohl May 14 '13 at 23:11
up vote 13 down vote accepted

Yes, that's the way it's supposed to be. mysqld_safe spawns a mysql-user run daemon (mysqld).

share|improve this answer
Great! Thanks for this clarification – Professor Frink Oct 2 '09 at 3:04

If you take a peek into the contents of mysqld_safe you'll find that it is merely a shell script wrapper for launching mysqld.

share|improve this answer
Oh,... if you look inside mysqld_safe it does quite a bit more than a mere wrapper. – Mike Kormendy Oct 29 '15 at 2:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.