On Wed, 2012-08-08 at 09:58 +0200, Zdenek Salvet wrote:
> On Tue, Aug 07, 2012 at 18:12:11 +0200, Lukas Hejtmanek wrote:
> > well, ok, thanks for anwsers. However, it seems that while NFS server's name
> > is server-home.domain.com (floating name), and true hostname is
> > server1.domain.com, it does not matter that callback is authenticated with
> > server1.domain.com instead of server-home.domain.com.
> >
> > Is this expected? Or is it a bug?
>
> It does matter, callback client name must match the name NFS client uses
> for server.
>
> 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?
Why should we care?
--
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�����٥
