ctdb-scripts: Be careful when generating unique pids for stack traces

sort expects the data to be line based, so make it so.

Signed-off-by: Amitay Isaacs <amitay@gmail.com>
Reviewed-by: Michael Adam <obnox@samba.org>

diff --git a/ctdb/config/debug_locks.sh b/ctdb/config/debug_locks.sh
index 8092d93034531bf22a95a99920e34e844a13552b..54b52ed146479d1ad6559816a394cc1d3246e729 100755 (executable)
--- a/ctdb/config/debug_locks.sh
+++ b/ctdb/config/debug_locks.sh
@@ -51,7 +51,7 @@ loadconfig ctdb
            pids=$(echo "$out" | grep -v "W$" | grep "$db" | grep -v ctdbd | awk '{print $1}')
            all_pids="$all_pids $pids"
        done
-       pids=$(echo $all_pids | sort -u)
+       pids=$(echo $all_pids | tr " " "\n" | sort -u)
 
        # For each process waiting, log stack trace
        for pid in $pids ; do