On 1/27/22 9:13 AM, Francis.Montagnac(a)inria.fr wrote:
Hi.
On Thu, 27 Jan 2022 08:10:53 -0600 Robert Nichols wrote:
> On 1/26/22 7:15 PM, Gordon Messmer wrote:
>> What does the entry for that filesystem in /proc/mounts look like? It should
have negotiated mount options that shed some light.
>> Maybe add the "sec=sys" mount option to the client.
> Looks like "sec=sys" is already in there:
> plugh-3g:/srv/shared /Public nfs4
rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.172,local_lock=none,addr=192.168.43.49
0 0
What about using nfs3 ?
You will not have any problem mapping lognames/uids/gids.
Indeed, "-o vers=3" does work and show the correct user and group names.
Thanks.
Of course, I'd still like to know why this system is locked to domain
"localdomain" and nothing can change that.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.