I just noticed that the underlying upstart issue mentioned in #8 is
already described by https://bugs.launchpad.net/upstart/+bug/530779. I
won't mark this as a duplicate though - the workaround described here
may be useful until the upstart bug is fixed.
--
Race condition in statd.conf
https://b
Tested on Maverick alpha 3 and confirmed that this bug is still present.
Debdiff for Maverick attached.
** Patch added: "nfs-utils_1.2.2-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/610863/+attachment/1497666/+files/nfs-utils_1.2.2-1ubuntu2.debdiff
--
Race condi
** Description changed:
- Binary package hint: mountall
+ Binary package hint: nfs-common
+ nfs-common version: 1:1.2.0-4ubuntu4
- On my Lucid system with latest updates, NFS filesystems sometimes fail to
mount successfully at boot. After a boot where the NFS mounts fail, the
mountall proce
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: mountall
On my Lucid system with latest updates, NFS filesystems sometimes fail to
mount successfully at boot. After a boot where the NFS mounts fail, the
mountall process is still running w
** Tags added: patch
--
Race condition in statd.conf
https://bugs.launchpad.net/bugs/610863
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listin
The above patch adds a post-start script that loops until the statd
parent process has exited. This is the best workaround that I can think
of. It doesn't seem possible to just wait() for the process with the
current implementation of upstart's "expect fork" feature.
Suggestion for a better appr
