Adding the explicit user (root) used to run sanlock makes runuser
acquire the supplementary groups for the process also at boot time.
Signed-off-by: Federico Simoncelli <fsimonce(a)redhat.com>
---
init.d/sanlock | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/init.d/sanlock b/init.d/sanlock
index 636d581..7521ae5 100644
--- a/init.d/sanlock
+++ b/init.d/sanlock
@@ -40,7 +40,7 @@ start() {
fi
echo -n $"Starting $prog: "
- daemon $prog daemon $SANLOCKOPTS
+ daemon --user root $prog daemon $SANLOCKOPTS
retval=$?
echo
[ $retval -eq 0 ] && touch $lockfile
--
1.7.1