summaryrefslogtreecommitdiff
path: root/ctdb/config
diff options
context:
space:
mode:
authorMartin Schwenke <martin@meltin.net>2018-04-30 16:01:57 +1000
committerMartin Schwenke <martins@samba.org>2018-05-01 13:31:18 +0200
commit32430f84159a02f3f6cadd325bcac92b44e0c8dc (patch)
tree82e02e77a5a1bb816f426aa1c13a3771204dbb4a /ctdb/config
parent8c43ce74948e0b218e19f677670238490dd93d69 (diff)
downloadsamba-32430f84159a02f3f6cadd325bcac92b44e0c8dc.tar.gz
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 <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
Diffstat (limited to 'ctdb/config')
-rwxr-xr-xctdb/config/ctdbd_wrapper9
1 files changed, 0 insertions, 9 deletions
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"