Open System Services NFS SCF Reference Manual

SCF Commands for OSS NFS
Open System Services NFS SCF Reference Manual—522582-001
2-19
Considerations
allowed during access checking because anyone who can become the root user on
their workstation can gain access to any remote file. If TRUE, remote root users
are allowed access to the server’s files with super-ID privileges. If FALSE, requests
from remote root users are treated as requests from the NFS nobody user (user ID
65534). Note that the FALSE value is contingent on the definition of user ID 65534
as the nobody user ID. To prevent super-ID permission during access checking, a
nobody user ID must be defined.
The default value is FALSE.
SWAP file-name
specifies a file used to hold the server process’s virtual data. This attribute allows
you to specify a permanent file for swapping the data stack and to specify a different
volume for the swap file. See the RUN command in the TACL Reference Manual
for more information about specifying a swap file.
UPSHIFT { TRUE | FALSE }
specifies whether file names on the NonStop Himalaya system are upshifted when
presented to NFS clients.
The default value is FALSE.
WRITE-THRU { TRUE | FALSE }
specifies whether data written by NFS clients to NonStop Himalaya systems is
written to cache or directly to disk. Configurations involving high-performance
applications should set this parameter to TRUE while those involving high-
reliability applications should set this parameter to false.
The default value is FALSE.
Considerations
Consider the following points when using the ADD SERVER command:
•
ADD SERVER is a sensitive command requiring super-group access.
•
You cannot use object-name templates to specify object names with the ADD
SERVER command.
•
NFS pass-through server processes always refer to the ZNFSUSR and ZNFSUSR1
files that are on the system they are running on. If the configuration includes pass-
through servers that are on a different Expand node than the one that the manager
process is on, the ZNFSUSR and ZNFSUSR1 files from the manager node must be
copied to the server node and properly secured. Each time any USER objects are
changed, the files must be copied over again for the remote Expand server to receive
the changes.
Table 2-2 describes the interactions between the "nobody" alias and the NULL-ALIAS-
OK parameter.