77
78 lockd_servers=num
79 Maximum number of concurrent lockd requests. The default is 256.
80
81 lockd_retransmit_timeout=num
82 Retransmit timeout, in seconds, before lockd retries. The
83 default is 5.
84
85 grace_period=num
86 Grace period, in seconds, that all clients (both NLM and NFSv4)
87 have to reclaim locks after a server reboot. This parameter also
88 controls the NFSv4 lease interval. The default is 90.
89
90 mountd_listen_backlog=num
91 Set the connection queue length for mountd over a connection-
92 oriented transport. The default value is 64.
93
94 mountd_max_threads=num
95 Maximum number of threads for mountd. The default value is 16.
96
97 Setting nfsmapid_domain
98 As described above, the setting for nfsmapid_domain overrides the domain
99 used by nfsmapid(1M) for building and comparing outbound and inbound
100 attribute strings, respectively. This setting overrides any other
101 mechanism for setting the NFSv4 domain. In the absence of a
102 nfsmapid_domain setting, the nfsmapid(1M) daemon determines the NFSv4
103 domain as follows:
104
105 o If a properly configured /etc/resolv.conf (see resolv.conf(4))
106 exists, nfsmapid queries specified nameserver(s) for the domain.
107
108 o If a properly configured /etc/resolv.conf (see resolv.conf(4))
109 exists, but the queried nameserver does not have a proper record of
110 the domain name, nfsmapid attempts to obtain the domain name through
111 the BIND interface (see resolver(3RESOLV)).
112
113 o If no /etc/resolv.conf exists, nfsmapid falls back on using the
114 configured domain name (see domainname(1M)), which is returned with
115 the leading domain suffix removed. For example, for
116 widgets.sales.acme.com, sales.acme.com is returned.
128 literal id's. For example, the UID 12345 is encoded as 12345.
129
130 o nfsmapid ignores the "domain" portion of the inbound attribute string
131 and performs name service lookups only for the user or group. If the
132 user/group exists in the local system name service databases, then
133 the proper uid/gid will be mapped even when no domain has been
134 configured.
135
136 This behavior implies that the same administrative user/group domain
137 exists between NFSv4 client and server (that is, the same uid/gid's
138 for users/groups on both client and server). In the case of
139 overlapping id spaces, the inbound attribute string could potentially
140 be mapped to the wrong id. However, this is not functionally
141 different from mapping the inbound string to nobody, yet provides
142 greater flexibility.
143
144 SEE ALSO
145 lockd(1M), mount_nfs(1M), mountd(1M), nfsd(1M), nfsmapid(1M),
146 sharectl(1M), smf(5)
147
148 NexentaStor December 16, 2016 NexentaStor
|
77
78 lockd_servers=num
79 Maximum number of concurrent lockd requests. The default is 256.
80
81 lockd_retransmit_timeout=num
82 Retransmit timeout, in seconds, before lockd retries. The
83 default is 5.
84
85 grace_period=num
86 Grace period, in seconds, that all clients (both NLM and NFSv4)
87 have to reclaim locks after a server reboot. This parameter also
88 controls the NFSv4 lease interval. The default is 90.
89
90 mountd_listen_backlog=num
91 Set the connection queue length for mountd over a connection-
92 oriented transport. The default value is 64.
93
94 mountd_max_threads=num
95 Maximum number of threads for mountd. The default value is 16.
96
97 mountd_port=num
98 The IP port number on which mountd should listen. The default
99 value is 0, which means it should use a default binding.
100
101 statd_port=num
102 The IP port number on which statd should listen. The default
103 value is 0, which means it should use a default binding.
104
105 Setting nfsmapid_domain
106 As described above, the setting for nfsmapid_domain overrides the domain
107 used by nfsmapid(1M) for building and comparing outbound and inbound
108 attribute strings, respectively. This setting overrides any other
109 mechanism for setting the NFSv4 domain. In the absence of a
110 nfsmapid_domain setting, the nfsmapid(1M) daemon determines the NFSv4
111 domain as follows:
112
113 o If a properly configured /etc/resolv.conf (see resolv.conf(4))
114 exists, nfsmapid queries specified nameserver(s) for the domain.
115
116 o If a properly configured /etc/resolv.conf (see resolv.conf(4))
117 exists, but the queried nameserver does not have a proper record of
118 the domain name, nfsmapid attempts to obtain the domain name through
119 the BIND interface (see resolver(3RESOLV)).
120
121 o If no /etc/resolv.conf exists, nfsmapid falls back on using the
122 configured domain name (see domainname(1M)), which is returned with
123 the leading domain suffix removed. For example, for
124 widgets.sales.acme.com, sales.acme.com is returned.
136 literal id's. For example, the UID 12345 is encoded as 12345.
137
138 o nfsmapid ignores the "domain" portion of the inbound attribute string
139 and performs name service lookups only for the user or group. If the
140 user/group exists in the local system name service databases, then
141 the proper uid/gid will be mapped even when no domain has been
142 configured.
143
144 This behavior implies that the same administrative user/group domain
145 exists between NFSv4 client and server (that is, the same uid/gid's
146 for users/groups on both client and server). In the case of
147 overlapping id spaces, the inbound attribute string could potentially
148 be mapped to the wrong id. However, this is not functionally
149 different from mapping the inbound string to nobody, yet provides
150 greater flexibility.
151
152 SEE ALSO
153 lockd(1M), mount_nfs(1M), mountd(1M), nfsd(1M), nfsmapid(1M),
154 sharectl(1M), smf(5)
155
156 NexentaStor December 18, 2016 NexentaStor
|