summaryrefslogtreecommitdiffstats
path: root/ctdb/config
diff options
context:
space:
mode:
authorMartin Schwenke <martin@meltin.net>2013-07-30 16:21:36 +1000
committerAmitay Isaacs <amitay@gmail.com>2013-08-14 15:57:03 +1000
commit5459cdc8a660ade0d92de0a06b9c5dfa97a7e0f9 (patch)
treec991abb1c942276c11eae79fbd2e96456d226967 /ctdb/config
parentd63cf0e7a7e7879a6794d2abdc03821be7f5c0d2 (diff)
downloadsamba-5459cdc8a660ade0d92de0a06b9c5dfa97a7e0f9.tar.gz
samba-5459cdc8a660ade0d92de0a06b9c5dfa97a7e0f9.tar.xz
samba-5459cdc8a660ade0d92de0a06b9c5dfa97a7e0f9.zip
eventscripts: When restarting the nfslock service only show output of start
That is, /dev/null the "stop" output. This is consistent with the way CTDB generally deals with the output when stopping a service. It also makes updating the eventscript unit tests easier. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit c7332526b1b488abefeb4be78a7cd3f2f9abc451)
Diffstat (limited to 'ctdb/config')
-rwxr-xr-xctdb/config/functions4
1 files changed, 2 insertions, 2 deletions
diff --git a/ctdb/config/functions b/ctdb/config/functions
index eabc940459..7c525884f5 100755
--- a/ctdb/config/functions
+++ b/ctdb/config/functions
@@ -861,7 +861,7 @@ startstop_nfslock() {
service nfsserver stop > /dev/null 2>&1
;;
restart)
- service nfsserver stop
+ service nfsserver stop > /dev/null 2>&1
service nfsserver start
;;
esac
@@ -875,7 +875,7 @@ startstop_nfslock() {
service nfslock stop > /dev/null 2>&1
;;
restart)
- service nfslock stop
+ service nfslock stop > /dev/null 2>&1
service nfslock start
;;
esac