Blame SOURCES/0051-run-Actually-use-timeout-foreground-option-RHBZ-1025.patch

cd6068
From 753df24b8f796d9cd35c64fc2725e322ef998327 Mon Sep 17 00:00:00 2001
cd6068
From: "Richard W.M. Jones" <rjones@redhat.com>
cd6068
Date: Mon, 27 Jan 2014 21:58:42 +0000
cd6068
Subject: [PATCH] run: Actually use timeout --foreground option (RHBZ#1025269).
cd6068
cd6068
The following commit managed to not actually add the --foreground
cd6068
option to the timeout command, just test for it.  Add it this time.
cd6068
cd6068
  commit 681488877456b83f039dc518861f29ab4e1857f0
cd6068
  Author: Richard W.M. Jones <rjones@redhat.com>
cd6068
  Date:   Thu Dec 19 08:21:53 2013 +0000
cd6068
cd6068
    run: Use timeout --foreground option.
cd6068
cd6068
    If timeout doesn't have this option (RHEL 6) don't use timeout at all.
cd6068
cd6068
    Attempt to fix RHBZ#1025269.
cd6068
cd6068
(cherry picked from commit e3f72805d108c601280b889692c47d7d825e6079)
cd6068
---
cd6068
 run.in | 2 +-
cd6068
 1 file changed, 1 insertion(+), 1 deletion(-)
cd6068
cd6068
diff --git a/run.in b/run.in
cd6068
index 5a45888..b0ad905 100755
cd6068
--- a/run.in
cd6068
+++ b/run.in
cd6068
@@ -212,7 +212,7 @@ if timeout --help >/dev/null 2>&1; then
cd6068
     if timeout --foreground 2 sleep 0 >/dev/null 2>&1; then
cd6068
         # Does this version of timeout have the -k option?  (Not on RHEL 6)
cd6068
         if timeout -k 10s 10s true >/dev/null 2>&1; then
cd6068
-            timeout="timeout -k $timeout_kill $timeout_period"
cd6068
+            timeout="timeout --foreground -k $timeout_kill $timeout_period"
cd6068
         fi
cd6068
     fi
cd6068
 fi
cd6068
-- 
cd6068
1.8.3.1
cd6068