Technical data

NFS Server
20.5 Managing the MOUNT Service
You can customize the operation of the MOUNT service by using SYSCONFIG to
modify the attributes listed in Table 20–1.
Table 20–1 MOUNT Attributes
Attribute Description
mountd_option_a Verifies the Internet addresses of hosts that make mount and
unmount requests. If a client’s address cannot be translated
into a host name by the
gethostbyaddr( ) function and is
then translated back into the same Internet address by the
gethost-byname( ) function, the request is rejected.
Requires name resolution to be enabled.
mountd_option_d Turns on Internet address verification and domain checking. If
you are running the BIND service, MOUNT verifies that a host
making a mount or unmount request is in the server’s domain.
mountd_option_i
Verifies the Internet address of hosts that make mount and
unmount requests. If a client’s address cannot be translated into
a host name by the
gethostbyaddr( ) function, the request is
rejected.
Requires name resolution to be enabled.
If the
mountd_option_i attribute is not set, and a client’s
address cannot be translated, the address is converted to a string
in the form xx.xx.xx.xx. This allows users to access exported file
systems that have a wildcard (*) (allow everybody) as their host
list.
The
mountd_option_i attribute is automatically enabled when
either the
mountd_option_d or the mountd_option_s attribute
is specified.
mountd_option_n Allows nonroot mount requests to be served. In previous versions
of TCP/IP Services, the servicing of nonroot mount requests was
allowed by default. With this version, this attribute must be set to
allow nonroot mount requests.
Specify this attribute only if there are clients (such as desktop
computers) that require it.
mountd_option_s Turns on Internet address verification and subdomain checking.
If you are running the BIND service, the MOUNT service verifies
that a host making a mount or unmount request is in the server’s
domain or subdomain.
See Section 20.12 for information about using the SYSCONFIG command.
20.6 Registering Users and Hosts
In a NFS environment shared by UNIX hosts, a common user authorization
domain may be used. In this configuration, each user’s UID is unique for all
the hosts. On OpenVMS, however, the user authorization file (UAF) cannot
be shared, but client user identifiers must be mapped to OpenVMS accounts.
Therefore, users on client hosts must have corresponding OpenVMS accounts on
the OpenVMS NFS server.
To establish this common allocation on OpenVMS, each client UID must be
mapped to a unique OpenVMS account. This arrangement requires a separate
OpenVMS account for each NFS client. It is possible to use the same OpenVMS
account for multiple users, but this is not recommended for accounts in which
users have read or edit access to files.
NFS Server 20–9