Package: mysql-server
Version: 5.5.37-0+wheezy1
Severity: important
Hi!
This is a followup to bug #208364. #208364 added a patch which make mysqld_safe
respond to signals and nicely terminate mysqld. The issue is that it does not
cover the case when --skip-syslog --log-error is used to run mysqld_safe. "&
wait" is missing in the command line in that code path. Adding it solves the
issue.
Mitar
-- System Information:
Debian Release: 7.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages mysql-server depends on:
ii mysql-server-5.5 5.5.37-0+wheezy1
mysql-server recommends no packages.
mysql-server suggests no packages.
-- no debconf information
--- mysqld_safe.orig 2014-07-06 23:05:31.378738591 -0700
+++ mysqld_safe 2014-07-06 23:05:12.158643283 -0700
@@ -143,7 +143,7 @@
eval_log_error () {
cmd="$1"
case $logging in
- file) cmd="$cmd >> "`shell_quote_string "$err_log"`" 2>&1" ;;
+ file) cmd="$cmd >> "`shell_quote_string "$err_log"`" 2>&1 & wait" ;;
syslog)
# mysqld often prefixes its messages with a timestamp, which is
# redundant when logging to syslog (which adds its own timestamp)
