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
** Branch linked: lp:ubuntu/nfs-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/611397
Title:
gssd does not start reliably at boot if /usr is on a separate
partition
To manage notifications a
** Branch unlinked: lp:ubuntu/natty/nfs-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/611397
Title:
gssd does not start reliably at boot if /usr is on a separate
partition
To manage notific
** Summary changed:
- gssd does not start
+ gssd does not start reliably at boot if /usr is on a separate partition
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/611397
Title:
gssd does not start r
You may also refer to LP #643289 posts #2, #3, #4, which include (among
others) a fix for gssd start-up problems. Please note that all of #2,
#3, #4 should be applied to make it work.
While I have not tested my gssd fix as intensely as similar ones for
idmapd/statd, all share major functionality,
There are no particular major gotchas, although there's no clean way
today to handle -dev packages for libraries in /lib. It's more that
moving all of these files to /lib requires touching lots of packages,
will take some time to finish, *and* is not a complete solution because
gssd still needs to
I personally don't see an issue with putting all of those libs in /lib
and binaries in /sbin, since they ultimately support mounting
filesystems other than /.
I have to wonder if those with more experience can shed light on any
hidden gotchyas there. I do see that rpc.gssd has a lot of libs in /us
But a solution such as 525154 does not solve the problem pointed out in
comment #2 and that's that /usr should be mountable as an NFS4
filesystem. Yes, that means moving all binaries and libraries necessary
to /sbin and /lib. Is that really a problem?
--
You received this bug notification becau
** Branch linked: lp:ubuntu/nfs-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/611397
Title:
gssd does not start
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
This bug probably needs a similar solution as bug #525154.
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided => High
** Changed in: nfs-utils (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
On Fri, Jul 30, 2010 at 09:31:46AM -, Christoph wrote:
> A possible solution is to move rpc.gssd from /usr/sbin to /sbin. As it
> is even possible that /usr is imported by NFS4, also rpc.idmapd should
> be moved from /usr/sbin to /sbin.
That's only a solution if we move all the dependency libr
A possible solution is to move rpc.gssd from /usr/sbin to /sbin. As it
is even possible that /usr is imported by NFS4, also rpc.idmapd should
be moved from /usr/sbin to /sbin.
--
gssd does not start
https://bugs.launchpad.net/bugs/611397
You received this bug notification because you are a member
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/52699380/Dependencies.txt
--
gssd does not start
https://bugs.launchpad.net/bugs/611397
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
13 matches
Mail list logo
