Bug #1815 Bad start command in /etc/init.d/mysql
Submitted: 12 Nov 2003 7:42 Modified: 13 Dec 2003 17:29
Reporter: Dmitry Roslyakov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:4.0.16 OS:Linux (Linux)
Assigned to: Michael Widenius CPU Architecture:Any

[12 Nov 2003 7:42] Dmitry Roslyakov 
Description:
/usr/src/redhat/SOURCES/mysql-4.0.16/support-files/mysql.server.sh
line 148:
 $bindir/mysqld_safe --datadir=$datadir --pid-file=$pid_file &
should be:
 $bindir/mysqld_safe --datadir=$datadir --pid-file=$pid_file >/dev/null 2>&1 &
as in 3.x releases.
Otherwise, if output of "/etc/init.d/mysql start" (or output of installing rpm, where mysql starts in post-installing script) is piped into script which reads stdin - pipe is never closed.

How to repeat:
/etc/init.d/mysql stop
/etc/init.d/mysql start | cat -

Pipe is not closed after mysqld starts.

Suggested fix:
Just to fix one line, as described above.
[13 Dec 2003 17:29] Michael Widenius 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Fix will be in 4.0.17