NFS Services Administrator's Guide

Troubleshooting NFS Services
Common Problems with NIS+
Chapter 8 321
If You Have Insufficient Memory or Disk Space
As a short-term solution to free up memory, kill all unnecessary
windows and processes. If necessary, exit your windowing system
and work from the terminal command line.
Use the ps -el command to check the size of running processes.
Sometimes programs develop memory leaks and grow very large. If
necessary, compare the size of processes on your host with processes
on a host that is not having memory problems to determine whether
the processes on your host are growing too large.
As a long-term solution, install more memory or swap space, or move
your NIS+ server to a system that has more memory or swap space.
If you have a shortage of disk space, clean out the /tmp directory and
remove any unnecessary files. Remove core files from the root
directory and home directories.
If you do not checkpoint your transaction log regularly, it becomes
very large. However, in order to checkpoint your transaction log, you
need sufficient disk space to allow NIS+ to make a complete copy of
the log before removing it. You might have to add disk space to your
server before checkpointing the log.
To checkpoint the log, issue the nisping -Ca command. If your
transaction log is large, or if you have a large number of replica
servers, the nisping command can take a long time. It is
recommended that you create a cron job to run nisping -Ca every
night while the network is not busy.