Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 May 2020 12:09:17 -0400
From:      Greg Veldman <freebsd@gregv.net>
To:        Norman Gray <norman.gray@glasgow.ac.uk>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: Documentation and debugging for NFSv4
Message-ID:  <20200528160917.GU1068@aurora.gregv.net>
In-Reply-To: <0E8D01CC-8BB3-456A-92C0-019F4B9AF447@glasgow.ac.uk>
References:  <20200526172613.GN1068@aurora.gregv.net> <6FE7F8A1-F296-4B85-A7C8-E360F8D559B6@glasgow.ac.uk> <20200526182550.GP1068@aurora.gregv.net> <0E8D01CC-8BB3-456A-92C0-019F4B9AF447@glasgow.ac.uk>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, May 28, 2020 at 04:58:06PM +0100, Norman Gray wrote:
> Also: It's the wrong list to ask this on, but would you happen to have 
> any pointers on getting this NFS-domain configuration working on CentOS 
> or similar machines?  I can find nothing intermediate between the RFC 
> and the nfsidmap tool & idmap.conf manpages.  Doing the obvious 
> configuration doesn't work, and even the debugging syslog messages give 
> few clues about what, precisely, is wrong.

On most distros (including CentOS I think) the daemon name is
rpc.idmapd and its config file is /etc/idmapd.conf.  In theory
you should only have to set the "Domain" keyword in the "General"
section of that file.  In practice, it's often not that easy.
I've typically found that if you run it as:

# rpc.idmapd -f -vvv

you're likely to at least get enough debug into to point you
in the right direction. ;-)

Good luck.

-- 
Greg Veldman



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20200528160917.GU1068>