On Thu, 2012-08-09 at 12:38 -0400, J. Bruce Fields wrote:
> On Thu, Aug 09, 2012 at 04:30:53PM +0000, Myklebust, Trond wrote:
> > On Thu, 2012-08-09 at 18:28 +0200, Lukas Hejtmanek wrote:
> > > On Thu, Aug 09, 2012 at 03:53:01PM +0000, Myklebust, Trond wrote:
> > > > 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.
> > > >
> > > > 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.
> > >
> > > hmm, if both rpc.gssd and rpc.svcgssd are needed on clients and servers, isn't
> > > it worth of merging them into a single process?
> >
> > You don't need rpc.gssd to use rpcsec_gss with NFSv3, nor do you need it
> ^^^^^^^^
>
> You meant rpc.svcgssd, unless you were thinking about the nfsd side.
Yes.
> > if you're not intending on using delegations with NFSv4.
>
> Though the default should be to support delegations.
Right, but that isn't a justification for making it impossible to run
without rpc.svcgssd if you don't need it.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
