From f97ae47b8a4dd7b4959a019adf148390e3a182cf Mon Sep 17 00:00:00 2001 From: Tobias Klausmann Date: Fri, 30 Sep 2016 16:15:45 +0200 Subject: [PATCH] sys-process/cronbase: second attempt at fixing bug 595492 In the case of a stale lockfile, the old code still produces error messages: /usr/sbin/run-crons: line 61: /proc/6450/cmdline: No such file or directory This change should dodge that scenario. --- .../{cronbase-0.3.7-r2.ebuild => cronbase-0.3.7-r3.ebuild} | 0 sys-process/cronbase/files/run-crons-0.3.7 | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) rename sys-process/cronbase/{cronbase-0.3.7-r2.ebuild => cronbase-0.3.7-r3.ebuild} (100%) diff --git a/sys-process/cronbase/cronbase-0.3.7-r2.ebuild b/sys-process/cronbase/cronbase-0.3.7-r3.ebuild similarity index 100% rename from sys-process/cronbase/cronbase-0.3.7-r2.ebuild rename to sys-process/cronbase/cronbase-0.3.7-r3.ebuild diff --git a/sys-process/cronbase/files/run-crons-0.3.7 b/sys-process/cronbase/files/run-crons-0.3.7 index c5f2d9ca7b33..ce8ff76e98bb 100755 --- a/sys-process/cronbase/files/run-crons-0.3.7 +++ b/sys-process/cronbase/files/run-crons-0.3.7 @@ -58,7 +58,7 @@ grab_lock() { # another run-crons process. # The tr call deletes null bytes so newer bash versions do not complain # about them. - cmdline1=$(tr -d '\0' < "/proc/${cronpid}/cmdline" 2>/dev/null) || : + cmdline1=$([ -r "/proc/${cronpid}/cmdline" ] && tr -d '\0' < "/proc/${cronpid}/cmdline" 2>/dev/null) || : cmdline2=$(tr -d '\0' < /proc/$$/cmdline) if [ "${cmdline1}" = "${cmdline2}" ] ; then # Whoa, another run-crons is really running. -- 2.26.2