HP Visualize c3600 IRIX to HP-UX Migration Guide - Page 104
Configuring and Administering an NFS Client
View all HP Visualize c3600 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 104 highlights
Network File System 4. If your server will be down for a long time, edit the /etc/fstab file on each client to comment out or remove any NFS mounts from the server you are planning to disable. This prevents the clients from attempting to mount directories from your server when the clients are rebooted. 5. If your server will be down for a long time, edit the /etc/auto_* files on each client to comment out or remove any automounts from the server you are planning to disable. Clients that automount the server's directories might not be listed by the showmount command. If you are using NIS to manage your automounter maps, edit the /etc/auto_* files on the NIS master server, and then issue the following commands to regenerate the maps and push them to the slave servers: # cd /var/yp # /usr/ccs/bin/make auto.mapname auto.mapname... 6. If you modified any direct automounter maps or the automounter master map, restart the automounter. 7. Issue the following command on the server to unexport all exported directories: # /usr/sbin/exportfs -au 8. On the NFS server, edit the /etc/rc.config.d/nfsconf file to set the NFS_SERVER variable to 0.This prevents the NFS server daemons from starting up when your system reboots. If your server will be down only a short time, this step is unnecessary. NFS_SERVER=0 9. Edit the /etc/inetd.conf file to comment out the line that contains rpc.mountd (if it exists) and the lines for the other RPC services. 10. Issue the following command to disable NFS server capability: # /sbin/init.d/nfs.server stop If your NFS server will be down for a short time, this procedure is not necessary. If the server is down for only a few minutes, and directories are hard-mounted on the clients, clients attempting access to the server will simply hang until it comes back up. Then, they will resume access to it as if nothing had happened. However, if the server will be down for a long time, NFS clients attempting access to it will have to interrupt their attempts, usually with [CTRL]-C. If directories are mounted with the nointr option, clients must reboot their systems in order to stop trying to access a down server. Configuring and Administering an NFS Client To Mount a Remote Directory Using a Standard NFS Mount 1. In the /etc/fstab file, use a text editor to add a line for each remote directory you want mounted on your system. If the /etc/fstab file does not exist, you will have to create it. A line in the /etc/fstab file has the following syntax: server:remote_directory local_directory nfs defaults 0 0 server:remote_directory local_directory nfs option[,option...] 0 0 2. If your system is already running as an NFS client, issue the following command to mount each remote directory you have added to the /etc/fstab file: # /usr/sbin/mount local_directory 99