summaryrefslogtreecommitdiff
path: root/ctdb/tests/simple/00_ctdb_onnode.sh
diff options
context:
space:
mode:
authorMartin Schwenke <martin@meltin.net>2012-03-29 14:54:22 +1100
committerMartin Schwenke <martin@meltin.net>2012-04-16 14:57:44 +1000
commitd4785e813aa5c2abf651c105edb1a8874afd1137 (patch)
treec0e5951028f2a97b0e11437befd7970aa506b429 /ctdb/tests/simple/00_ctdb_onnode.sh
parent7698a5105e0539f0bd1222f7787d2682aa2dcdf9 (diff)
downloadsamba-d4785e813aa5c2abf651c105edb1a8874afd1137.tar.gz
Tests - turn of time logging by default
We haven't seen problems related to time jumps for a long time. Turn this off by default. To switch it back on set $CTDB_TEST_TIME_LOGGING to any non-null value. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit 2aa9bbf3a52dde0707eb06acd91e57c8da5c717f)
Diffstat (limited to 'ctdb/tests/simple/00_ctdb_onnode.sh')
-rwxr-xr-xctdb/tests/simple/00_ctdb_onnode.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/ctdb/tests/simple/00_ctdb_onnode.sh b/ctdb/tests/simple/00_ctdb_onnode.sh
index fa5e25affcc..3d8221a58c0 100755
--- a/ctdb/tests/simple/00_ctdb_onnode.sh
+++ b/ctdb/tests/simple/00_ctdb_onnode.sh
@@ -31,7 +31,7 @@ onnode all onnode all true
# We're seeing some weirdness with CTDB controls timing out. We're
# wondering if time is jumping forward, so this creates a time log on
# each node that we can examine later if tests fail weirdly.
-if [ -n "$CTDB_TEST_REAL_CLUSTER" ] ; then
+if [ -n "$CTDB_TEST_REAL_CLUSTER" -a -n "$CTDB_TEST_TIME_LOGGING" ] ; then
echo "Starting time logging on each node..."
f="/var/log/ctdb.test.time.log"
onnode -p all "[ -f $f ] || while : ; do date '+%s %N' ; sleep 1 ; done >$f 2>&1 </dev/null &" &