Mailinglist Archive: opensuse (1174 mails)

[lynn <lynn@xxxxxxxxxxxx>]

On 01/03/2012 09:43 PM, Anders Johansson wrote:
> On Tuesday 03 January 2012 16:49:29 lynn wrote:
> > Hi
> > Yast NFS Client gives me the option to choose a share and select nfsv4.
> > If I select the share I want from the drop down list it will not mount
> > the share. I think the dialogue is wrong. e.g. if /home is exported and
> > I select /home from the drop down list it will not mount. For nfs4 it
> > should change /home to /
> >
> > As I see it, yast is trying to do this:
> >
> > mount -t nfs4 myserver:/home /somewhere
> >
> > but it should be doing this
> >
> > mount -t nfs4 myserver:/ /somewhere
> >
> > Is this a bug in Yast?
> Yes, it looks like a bug.
Is it important enough to bugzilla it?
> > I can mount it manually, but what should I put in fstab to make it mount?
> myserver:/ /somewhere nfs4 defaults 0 0
Thanks.

Whilst we're here, does the Kerberos stuff look after itself? I've 
kerberized nfs but in particular, should the nfs4 domainname relate to 
the Kerberos realm? (It doesn't seem to matter what you call it so long 
as it's set the same on server and clients.)

Also, is it intended that the Yast NFS Client set the Domain=domainname 
in /etc/idmapd.conf ? (Yast NFS Server does.) I'm not sure if this is 
another bug, but I had to change this manually on the client:

[General]
Verbosity=0
Pipefs-Directory=/var/lib/nfs/rpc_pipefs
#Domain=domainname
Domain=SOMETHING.ELSE
[Mapping]
Nobody-User=nobody
Nobody-Group=nobody

Sorry to be a pain.
L x

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx