From 32430f84159a02f3f6cadd325bcac92b44e0c8dc Mon Sep 17 00:00:00 2001 From: Martin Schwenke Date: Mon, 30 Apr 2018 16:01:57 +1000 Subject: ctdb-scripts: Drop CTDB_VALGRIND testing option This is too inflexible for general use. There is no use finding a new home for this in the new configuration scheme. Signed-off-by: Martin Schwenke Reviewed-by: Amitay Isaacs --- ctdb/config/ctdbd_wrapper | 9 --------- 1 file changed, 9 deletions(-) (limited to 'ctdb/config') diff --git a/ctdb/config/ctdbd_wrapper b/ctdb/config/ctdbd_wrapper index dca90172d26..f831afacb18 100755 --- a/ctdb/config/ctdbd_wrapper +++ b/ctdb/config/ctdbd_wrapper @@ -141,15 +141,6 @@ start() ulimit -n "$CTDB_MAX_OPEN_FILES" fi - if [ -n "$CTDB_VALGRIND" -a "$CTDB_VALGRIND" != "no" ] ; then - if [ "$CTDB_VALGRIND" = "yes" ] ; then - ctdbd="valgrind -q --log-file=/usr/local/var/log/ctdb_valgrind ${ctdbd}" - else - ctdbd="${CTDB_VALGRIND} ${ctdbd}" - fi - ctdb_options="${ctdb_options} --valgrinding" - fi - case "$CTDB_LOGGING" in syslog:udp|syslog:udp-rfc5424) logger -t ctdbd "CTDB is being run with ${CTDB_LOGGING}. If nothing is logged then check your syslogd configuration" -- cgit v1.2.1