NFS Services Administrator's Guide

Troubleshooting NFS Services
Logging and Tracing of NFS Services
Chapter 8350
NIS Logging
You can configure logging for the following NIS processes:
• ypxfr
• ypserv
• ypbind
• yppasswdd
Each message logged by these daemons can be identified by the date,
time, host name, process ID, and name of the function that generated the
message. You can direct logging messages from all these NIS daemons to
the same file.
To Control the Size of Log Files
Log files grow without bound, using up disk space. You might want to
create a cron job to truncate your log files regularly. Following is an
example crontab entry that empties the log file at 1:00 AM every
Monday, Wednesday, and Friday:
0 1 * * 1,3,5 cat /dev/null > log_file
For more information, type man 1M cron or man 1 crontab at the
HP-UX prompt.
To Stop and Start Logging of ypxfr
If ypxfr is run interactively from the command line, it logs messages to
standard output. If ypxfr is run by cron or by yppush, it logs messages
to the file /var/yp/ypxfr.log, if the file exists. To start logging of
ypxfr, issue the following command to make sure the
/var/yp/ypxfr.log file exists:
/usr/bin/touch /var/yp/ypxfr.log
To stop logging of ypxfr, remove the ypxfr.log file:
/usr/bin/rm /var/yp/ypxfr.log
You cannot redirect the logging output of ypxfr.
For more information, see the following man pages: ypxfr(1M),
cron(1M), and yppush(1M).