Version: 1.0.7-3
Tags: patch
The statd daemon changes its uid to match that of the file(s) (in)
/var/lib/nfs/. So if you change your /var/lib/nfs to be owned by, say,
"daemon", then you will see this bug in Sarge. Running the daemon
non-root is a good security feature, and security-conscious sysadmins
will use it. (I agree with #240689 that it should be the default.)
Obviously, the init script should support it, whether or not it is the
default.
The "stop" part of the script /etc/init.d/nfs-common stops the statd
daemon with "start-stop-daemon --stop --user 0 ...". This means that
if the daemon is not running as user 0 (root), then the stop script
will fail to stop the daemon. I see no good reason the script should
be so picky about the uid of the daemon processes.
The following patch updates the init.d script so that it always stops
the daemons, even if the daemons are running non-root. This is a more
general patch than the one in the original bug report.
--- nfs-utils-1.0.7/debian/nfs-common.init 2005-01-05 07:38:17.000000000
-0500
+++ debian/nfs-common.init 2005-05-17 04:59:42.000000000 -0400
@@ -71,11 +71,11 @@
then
printf " lockd"
start-stop-daemon --stop --oknodo --quiet \
- --name rpc.lockd --user 0 || true
+ --name rpc.lockd || true
fi
printf " statd"
start-stop-daemon --stop --oknodo --quiet \
- --name rpc.statd --user 0
+ --name rpc.statd
echo "."
;;
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
