System information

setting is sec= sys, which uses local UNIX UID s and GIDs by using AUT H_SY S to
authenticate NFS operations.
sec= krb5 uses Kerberos V5 instead of local UNIX UIDs and GID s to authenticate users.
sec= krb5i uses Kerberos V5 for user authentication and performs integrity checking of
NFS operations using secure checksums to prevent data tampering.
sec= krb5p uses Kerberos V5 for user authentication, integrity checking, and encrypts NFS
traffic to prevent traffic sniffing. This is the most secure setting, but it also involves the most
performance overhead.
t cp
Instructs the NFS mount to use the TCP protocol.
u d p
Instructs the NFS mount to use the UD P protocol.
For a complete list of options and more detailed information on each one, refer to man mo unt and
man nfs.
9.6. St art ing and St opping NFS
To run an NFS server, the rpcbi nd
[3]
service must be running. To verify that rpcbi nd is active, use
the following command:
# servi ce rpcbi nd status
If the rpcbi nd service is running, then the nfs service can be started. To start an NFS server, use
the following command:
# servi ce nfs start
nfsl o ck must also be started for both the NFS client and server to function properly. To start NFS
locking, use the following command:
# servi ce nfsl ock start
If NFS is set to start at boot, ensure that nfsl o ck also starts by running chkco nfi g --l i st
nfsl o ck. If nfsl o ck is not set to o n, this implies that you will need to manually run the servi ce
nfsl o ck start each time the computer starts. To set nfsl o ck to automatically start on boot, use
chkco nfi g nfsl o ck o n.
nfsl o ck is only needed for NFSv2 and NFSv3.
To stop the server, use:
# servi ce nfs sto p
The restart option is a shorthand way of stopping and then starting NFS. This is the most efficient
way to make configuration changes take effect after editing the configuration file for NFS. To restart
the server type:
Red Hat Ent erprise Lin ux 6 St orage Admin ist rat io n G uide
62