sys-process/cronbase: Fix the parall-job check once and for all.

Thanks to Dan Goodliffe for suggesting this approach.

Gentoo-Bug: 595492

diff --git a/sys-process/cronbase/cronbase-0.3.7-r4.ebuild b/sys-process/cronbase/cronbase-0.3.7-r5.ebuild
similarity index 100%
rename from sys-process/cronbase/cronbase-0.3.7-r4.ebuild
rename to sys-process/cronbase/cronbase-0.3.7-r5.ebuild

diff --git a/sys-process/cronbase/files/run-crons-0.3.7 b/sys-process/cronbase/files/run-crons-0.3.7
index 958ef06c1ef728f13a1a4848372c37217969dc9b..902794e19e6f744bb7aa9f928e5ee4d61e39ac3b 100755 (executable)
--- a/sys-process/cronbase/files/run-crons-0.3.7
+++ b/sys-process/cronbase/files/run-crons-0.3.7
@@ -56,11 +56,7 @@ grab_lock() {
 
                # This is better than kill -0 because we can verify that it's really
                # another run-crons process.
-               # The tr call deletes null bytes so newer bash versions do not complain
-               # about them.
-               cmdline1=$(sed -e 's/\0/ /g' "/proc/${cronpid}/cmdline" 2>/dev/null) || :
-               cmdline2=$(sed -e 's/\0/ /g' /proc/$$/cmdline)
-               if [ "${cmdline1}" = "${cmdline2}" ] ; then
+               if diff -qs /proc/{${cronpid},$$}/cmdline > /dev/null 2>&1; then
                        # Whoa, another run-crons is really running.
                        return 1
                fi