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>

diff --git a/config/functions b/config/functions
index eabc9404595611872c2dc3428053525bf578c934..7c525884f5ff95173fc515f44b36c2221b480805 100755 (executable)
--- a/config/functions
+++ b/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