On 07/29/2015 10:28 PM, Chuck Lever wrote:
> Hi-
>
> At least for testing purposes, it would be great to be able to
> manage a system's NFSv4 domain name from the command line. I'm
> frequently asked how to determine a system's NFSv4 domain name,
> and I'm forced to answer something like this:
>
>> Linux does not currently have a command line tool for managing
>> the system's NFSv4 idmapping domain. Use:
>>
>> awk '/^Domain/ { print $3 }' < /etc/idmapd.conf
>>
>> If that fails to find anything, then use `dnsdomainname` . That
>> won't be helpful if the system has multiple i/f's.
>
>
> This doesn't even get into /proc/keys, or what to do to change
> the NFSv4 domainname, or the differences between rpc.idmapd and
> the keyring-based idmapper.
>
> Linux now has hostnamectl and other tools to manage a system's
> hostname and so on. Solaris has sharectl, which can display and
> update the nfs4mapid_domain.
>
> Does it make sense to extend the nfsidmap command to display and
> modify the NFSv4 domain name?
I would think so... All the tools (aka conf_XXX() calls) are there
and I think it would be relatively simple...
Another thing I always thought would be nice is a way
to show the existing uid/gid keys in a human format.
Now to see what keys exist one has to cat /proc/keys
which is not very readable...
steved.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
