Open System Services NFS Management and Operations Guide

Files

OSS NFS operation requires these types of files:

• NFS executable files

• RPC executable files

• NFS configuration and management files

• User ID translation files (ZNFSUSR and ZNFSUSR1)

• PCNFSD configuration file

• EMS templates for NFS and RPC

OSS NFS and RPC Executable Files

These OSS NFS executable files can be located anywhere in a NonStop system. The default location

after installation is $system.ZOSSNFS.

• NFSMGR – Manager process

• NFSMGR2 – Manager Helper process

• NFSLAN– LAN process

• NFSSVRHP – Server headpin process

• NFSSVRWB – Server workerbee process

• PCNFSD – PCNFSD process

• PCAUTHD – Authentication server process

• PCLPRD – Print spool server process

These OSS NFS executable files must be located in $SYSTEM.SYSTEM:

• ZNFSPTR – NFS PTrace product module

• ZNFSSCF – NFS SCF product module executable

• ZNFSTEXT – NFS SCF module help text

The locations for the RPC executable files PORTMAP and RPCINFO are:

• $SYSTEM.ZRPC.PORTMAP

• $SYSTEM.SYSTEM.RPCINFO

NOTE: OSS NFS does not support copying of an executable file from an NFS client that is

running as an OSS process on the operating system.

OSS NFS Configuration and Management Files

The OSS NFS manager processes keeps all configuration information (other than USER object

information) in files named ZZNFSnnn on the configuration subvolume (where n is a digit in the

range 0 through 9). Reserve the $SYSTEM.ZOSSNFS for use by OSS NFS. Start the OSS NFS

subsystem by using the purgedb option when running NFSMGR. This option purges the ZZNFSnnn

configuration files on that subvolume.

The subvolume containing the OSS NFS configuration files is determined by the configuration

parameter in the RUN command for NFSMGR. For detailed syntax information for the NFSMGR

RUN command, see Chapter 4 (page 36).

User ID Translation Files

The OSS NFS manager process uses the file ZNFSUSR (and its associated alternate-key file,

ZNFSUSR1) on $SYSTEM.ZOSSNFS to store information about USER objects. The USER objects

Processes and Files 17