Installation guide

Starting and Stopping NFS
67
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.
tcp
Instructs the NFS mount to use the TCP protocol.
udp
Instructs the NFS mount to use the UDP protocol.
For a complete list of options and more detailed information on each one, refer to man mount and
man nfs. For more information on using NFS via TCP or UDP protocols, refer to Section 10.9, “Using
NFS over TCP”.
10.5. Starting and Stopping NFS
To run an NFS server, the rpcbind
1
service must be running. To verify that rpcbind is active, use
the following command:
service rpcbind status
Note
Using service command to start, stop, or restart a daemon requires root privileges.
If the rpcbind service is running, then the nfs service can be started. To start an NFS server, use
the following command as root:
service nfs start
Note
nfslock must also be started for both the NFS client and server to function properly. To start
NFS locking, use the following command:
service nfslock start
If NFS is set to start at boot, ensure that nfslock also starts by running chkconfig --
list nfslock. If nfslock is not set to on, this implies that you will need to manually run the
service nfslock start each time the computer starts. To set nfslock to automatically
start on boot, use chkconfig nfslock on.
nfslock is only needed for NFSv2 and NFSv3.
To stop the server, use:
service nfs stop
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, as root, type: