I reproduced the issue using Steve Atwell's modification in /etc/init/rpc_pipefs.conf and I am able to reproduce the same issue in a stock Lucid install.
It looks like /etc/init/idmapd.conf needs also another if statement that checks whether the client is using nfsv4 or not. I made a small change to the upstart script and now I don't see the issue anymore. Idmapd start successfully and I am able to mount using krb5.
Here is what I did:
I've changed the last statement (script/end script) in /etc/init/idmapd.conf to the following:
script
if [ -f "$DEFAULTFILE" ]; then
. "$DEFAULTFILE"
#
# We also need to check in /etc/default/nfs-common if the client wants to use nfs4
#
if grep -q "NEED_IDMAPD=yes" $DEFAULTFILE ; then mount -t rpc_pipefs rpc_pipefs /var/lib/nfs/rpc_pipefs
fi
Hi Guys,
I reproduced the issue using Steve Atwell's modification in /etc/init/ rpc_pipefs. conf and I am able to reproduce the same issue in a stock Lucid install.
It looks like /etc/init/ idmapd. conf needs also another if statement that checks whether the client is using nfsv4 or not. I made a small change to the upstart script and now I don't see the issue anymore. Idmapd start successfully and I am able to mount using krb5.
Here is what I did: idmapd. conf to the following:
I've changed the last statement (script/end script) in /etc/init/
script nfs-common if the client wants to use nfs4
mount -t rpc_pipefs rpc_pipefs /var/lib/ nfs/rpc_ pipefs
if [ -f "$DEFAULTFILE" ]; then
. "$DEFAULTFILE"
#
# We also need to check in /etc/default/
#
if grep -q "NEED_IDMAPD=yes" $DEFAULTFILE ; then
fi
fi
exec rpc.idmapd
end script
Can you guys check on your side as well?
Leonardo