Public bug reported:
I have some user-mountable nfs entries in my /etc/fstab like this:
myserver:/srv/nfs/images /mnt/images nfs
defaults,user,noauto,intr,rsize=32768,wsize=32768 0 0
for this to work, statd (from nfs-common) needs to be running, but it is
not started at system startup
The scripts claim that it will be started
According to /etc/init/statd.conf rpc.statd should be started either if
some NFS filesystem will be mounted or if NEED_STATD is not "no"
When a user tries to mount a NFS share, statd will not be started:
u...@ubuntu:~$ mount /mnt/images
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
u...@ubuntu:~$
And setting NEED_STATD to yes in /etc/default/nfs-common will NOT start
statd on system startup...
I also tried a workaround: Putting "@reboot service start statd" into a system
cronjob which also does NOT work...
However, starting it as root manually works, and nfs mounts are working
afterwards
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nfs-common 1:1.2.0-4ubuntu4
Uname: Linux 2.6.34rc3-51-generic i686
Architecture: i386
Date: Mon May 17 22:25:57 2010
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: nfs-utils
** Affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 lucid
--
statd does not start automatically when needed nor can be forced to start on
boot
https://bugs.launchpad.net/bugs/581941
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
