Closed annunaki2k2 closed 11 years ago
There appears to have been new comment added to the upstream mysqld_safe.sh file that breaks the scripts__mysqld_safe.sh__signals.patch.
Changing it to the below worked for me: -- snip -- @@ -29,9 +29,8 @@ syslog_tag_mysqld=mysqld syslog_tag_mysqld_safe=mysqld_safe
-trap '' 1 2 3 15 # we shouldn't let anyone kill us
-trap '' 13 # not even SIGPIPE +trap '' 13 # we shouldn't let SIGPIPE kill us, other signals are handled properly later
@@ -135,7 +134,7 @@ -- snip --
Thanks for reporting this, this is now fixed.
There appears to have been new comment added to the upstream mysqld_safe.sh file that breaks the scripts__mysqld_safe.sh__signals.patch.
Changing it to the below worked for me: -- snip -- @@ -29,9 +29,8 @@ syslog_tag_mysqld=mysqld syslog_tag_mysqld_safe=mysqld_safe
-trap '' 1 2 3 15 # we shouldn't let anyone kill us
>> MCP_BUG33984
-trap '' 13 # not even SIGPIPE +trap '' 13 # we shouldn't let SIGPIPE kill us, other signals are handled properly later
<< MCP_BUG33984
MySQL-specific environment variable. First off, it's not really a umask,
@@ -135,7 +134,7 @@ -- snip --