Bug #33984 Trap SIGPIPE in mysqld_safe
Submitted: 22 Jan 2008 15:41 Modified: 6 May 2011 12:46
Reporter: Geert Vanderkelen Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: General Severity:S4 (Feature request)
Version:CGE-6.3 OS:Any
Assigned to: Magnus Blåudd CPU Architecture:Any
Tags: MCP

[22 Jan 2008 15:41] Geert Vanderkelen
It some situations it would be helpful to trap the SIGPIPE signal. For example when rcmd() is used to start the MySQL server, mysqld_safe would exit when the file descriptor is closed (and a SIGPIPE is send to the remote process..).

How to repeat:

Suggested fix:
===== mysqld_safe.sh 1.95 vs edited =====
< trap '' 1 2 3 15                      # we shouldn't let anyone kill us
> trap '' 1 2 3 13 15                   # we shouldn't let anyone kill us
[2 Apr 2008 12:25] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:


ChangeSet@1.2589, 2008-04-02 14:25:42+02:00, geert@cent01.kemuri.net +1 -0
    BUG#33984 Trap SIGPIPE in mysqld_safe
    Trapping also signal 13 or SIGPIPE preventing killing the mysqld_safe script.
[11 Apr 2008 14:12] Jon Stephens
Documented in the 5.1.24-ndb-6.3.13 changelog as follows:

        mysqld_safe now traps Signal 13 (SIGPIPE) so that this signal no longer
        kills the MySQL server process.

Left Patch Approved status unchanged pending further action/merges of the fix.
[28 Mar 2012 11:54] Magnus Blåudd
Fixed in 5.6.6