summaryrefslogtreecommitdiffstats
path: root/utils/idmapd
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2010-02-12 14:23:16 -0500
committerSteve Dickson <steved@redhat.com>2010-02-12 14:23:16 -0500
commit8f9493d13f884a62d7581326c1925a8171b3b0bd (patch)
tree3e60d02a969d3ae67d3fec277be9441cf806e32b /utils/idmapd
parent7b0e4faaf3169c69828d3f7769ed8ce9142e100b (diff)
downloadnfs-utils-8f9493d13f884a62d7581326c1925a8171b3b0bd.tar.gz
nfs-utils-8f9493d13f884a62d7581326c1925a8171b3b0bd.tar.xz
nfs-utils-8f9493d13f884a62d7581326c1925a8171b3b0bd.zip
This is the second iteration of this patch. The only difference here
is that this one has default_value call nfs_nfs_proto_family regardless of whether IPV6_SUPPORTED is set. When IPv6 is enabled, the Proto= config file option is treated as a netid, and the address family for lookups is selected based on that setting. The Defaultproto= option however still only affects the protocol setting for the sockets (IPPROTO_*) and not the address family. This patch makes it so that if someone sets the "Defaultproto=" option in the nfsmount.conf, it's used to determine the default address family for lookups as well as the protocol type. This gives users a way to force a particular address family to be used universally for mounts and brings the behavior of the Defaultproto= option in line with the Proto= option. Signed-off-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'utils/idmapd')
0 files changed, 0 insertions, 0 deletions