This bug was fixed in the package nfs-utils - 1:1.2.6-3ubuntu2
---------------
nfs-utils (1:1.2.6-3ubuntu2) quantal; urgency=low
[ Steve Langasek ]
* Adjust upstart jobs to treat TYPE=nfs and TYPE=nfs4 mounts identically,
since TYPE=nfs4 is considered deprecated.
* Fix various boot-time race conditions between mountall and nfs-utils by
moving handling of the 'mounting' events to separate gssd-mounting and
idmapd-mounting jobs. Requires mountall 2.41 or better to avoid deadlock
on boot. LP: #643289, LP: #611397.
* Fix the stop conditions: never stop on 'runlevel [06]' since that gives
the system no time to cleanly unmount nfs mounts; instead, stop only on
the unmounted-remote-filesystems event.
* Newer versions of gssd don't talk to portmap, so don't make the upstart
job depend on it.
* Add an instance to statd-mounting, and change it to just wait for statd
instead of trying to trigger it potentially out of order. This also means
we don't need to try to force portmap to start from statd.
[ Matthew L. Dailey ]
* Add "-e" (ticket expiry is error) option to rpc.gssd to prevent hangs due
to EKEYEXPIRED error from kernel on ticket expiry. LP: #794112
-- Stephane Graber <stgra...@ubuntu.com> Fri, 28 Sep 2012 13:58:43 -0400
** Changed in: nfs-utils (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/643289
Title:
idmapd does not starts to work after system reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/643289/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
