*** This bug is a duplicate of bug 525154 ***
https://bugs.launchpad.net/bugs/525154
** This bug is no longer a duplicate of bug 581941
statd does not start automatically when needed nor can be forced to start on
boot
** This bug has been marked a duplicate of bug 525154
mountall for
*** This bug is a duplicate of bug 581941 ***
https://bugs.launchpad.net/bugs/581941
** This bug has been marked a duplicate of bug 581941
statd does not start automatically when needed nor can be forced to start on
boot
* You can subscribe to bug 581941 by following this link:
** Changed in: nfs-utils (Ubuntu)
Status: New = Confirmed
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided = High
** Changed in: nfs-utils (Ubuntu)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
** Also affects: nfs-utils (Ubuntu Lucid)
Importance:
** Branch linked: lp:~clint-fewbar/ubuntu/natty/nfs-utils/wait-for-
local-filesystems
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690401
Title:
statd startup races with / becoming writable
--
So, the current statd.conf makes sure that its always running when
portmap is running with:
start on (started portmap or mounting TYPE=nfs)
stop on stopping portmap
It also makes sure, in case it was started on mounting TYPE=nfs before
portmap, that portmap is running, in the pre-start.
portmap
Also note that if there are locks remaining in /var/lib/nfs/sm/... and
this race occurs, sm-notify will fail to notify the nfs server about
locks, but exit 0 anyway. backup_hosts() will attempt to move the files
into sm.bak and, that having failed (non-fatally) due to a readonly
filesystem,
