ctdb-doc: Drop unnecessary, broken attempt at rpc.statd stack trace

There is a typo here, since there will be no process called "status".
Instead of fixing it, drop this because rpc.statd isn't the focus of
this monitoring check and when systemd is init rpc.statd isn't
restarted with nfs-ganesha.  It stays running, so a confusing stack
trace for rpc.statd is always logged.

Signed-off-by: Martin Schwenke <mschwenke@ddn.com>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>

diff --git a/ctdb/doc/examples/20.nfs_ganesha.check b/ctdb/doc/examples/20.nfs_ganesha.check
index b153acaedf92e45c5da417ee9fdcf864ebc30234..92112aff384a4a7b84544bc1138e067a68c8998b 100644 (file)
--- a/ctdb/doc/examples/20.nfs_ganesha.check
+++ b/ctdb/doc/examples/20.nfs_ganesha.check
@@ -4,5 +4,3 @@ unhealthy_after=1
 service_stop_cmd="$CTDB_NFS_CALLOUT stop nfs"
 service_start_cmd="$CTDB_NFS_CALLOUT start nfs"
 service_check_cmd="$CTDB_NFS_CALLOUT check nfs"
-# Ganesha initscript restarts rpc.statd and stack trace is desirable!
-service_debug_cmd="program_stack_traces status 5"