On Thu, Aug 09, 2012 at 03:53:01PM +0000, Myklebust, Trond wrote: > On Thu, 2012-08-09 at 10:45 -0400, J. Bruce Fields wrote: > > On Thu, Aug 09, 2012 at 10:06:42AM +0200, Zdenek Salvet wrote: > > > On Wed, Aug 08, 2012 at 01:18:09PM +0000, Myklebust, Trond wrote: > > > > > We don't see any hard failures because NFS protocol does > > > > > not depend on working callback RPCs, but no delegations are granted > > > > > (we had nfs-kernel-server package installed on clients before which masked > > > > > the bug). > > > > > > > > So your gripe that you object to us requiring you to run rpc.svcgssd in > > > > order to obtain server features such as NFSv4 callbacks? > > > > > > Absolutely not! Just thinking why we did not notice the problem earlier ... > > > > I wonder if there's anything we could do to make this more automatic, > > though: e.g., perhaps whichever scripts are launching one of the gss > > daemons should be replaced by one that launches both, since that's > > generally what you'll want for NFSv4.0. (Not necessary for other > > versions, but it doesn't hurt much.) > > > > Or perhaps they could be started on demand somehow. > > How is this any different to requiring that the user start rpc.statd > before launching an NFSv3 mount? Just document the requirement if it > isn't already clear enough, and we can move on. That's good enough, but it's always nice if there's some configuration we can skip. (Not that I'm volunteering.) > The other source of confusion here, was that the rpc.svcgssd was > delivered through a nfs-kernel-server package, which indicates that we > first and foremost need to educate the distro packagers. Yes, that's a mistake. The nfs-utils README is where we've been documenting daemon startup--I'll work on a patch. (And see if the man pages could use something too.) And somebody should ping Debian (nfs-kernel-server sounds like a Debian thing.) --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
