8.5. Starting and Stopping the NFS Server
8.5. Starting and Stopping the NFS Server Prerequisites For servers that support NFSv2 or NFSv3 connections, the rpcbind [1] service must be running. To verify that rpcbind is active, use the following command: To configure an NFSv4-only server, which does not require rpcbind , see Section 8.6.7, "Configuring an NFSv4-only Server" . On Red Hat Enterprise Linux 7.0, if your NFS server exports NFSv3 and is enabled to start at boot, you need to manually start and enable the nfs-lock service: On Red Hat Enterprise Linux 7.1 and later, nfs-lock starts automatically if needed, and an attempt to enable it manually fails. Procedures To start an NFS server, use the following command: To enable NFS to start at boot, use the following command: To stop the server, use: 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: After you edit the /etc/sysconfig/nfs file, restart the nfs-config service by running the following command for the new values to take effect: The try-restart command only starts nfs if it is currently running. This command is the equivalent of condrestart ( conditional restart ) in Red Hat init scripts and is useful because it does not start the daemon if NFS is not running. To conditionally restart the server, type: To reload the NFS server configuration file without restarting the service type:
systemctl status rpcbind systemctl start nfs-lock # systemctl enable nfs-lock systemctl start nfs systemctl enable nfs systemctl stop nfs systemctl restart nfs systemctl restart nfs-config systemctl try-restart nfs systemctl reload nfs