NFS Services Administrator's Guide

Troubleshooting NFS Services
Logging and Tracing of NFS Services
Chapter 8342
To Start and Stop rpc.mountd Logging
1. Issue the following commands to kill the rpc.mountd process and
restart it with logging turned on (PID is a process ID returned by the
ps command):
ps -ef | grep mountd
kill PID
/usr/sbin/rpc.mountd -l /var/adm/mountd.log
2. If you want rpc.mountd to log mount requests and mount failures as
well as errors, add the -t2 option to the rpc.mountd command, as in
the following example:
/usr/sbin/rpc.mountd -l /var/adm/mountd.log -t2
3. To stop logging, kill rpc.mountd and restart it without the -l
logfile and -t2 options.
If you do not specify the -l or-t option, rpc.mountd logs only errors to
/var/adm/mountd.log. If this file does not exist, rpc.mountd creates it.
rpc.mountd can share the same log file with the other NFS daemons.
For more information, type man 1M mountd at the HP-UX prompt.
To Start and Stop Detailed Logging of rpc.statd and rpc.lockd
To start detailed logging of rpc.statd and rpc.lockd while they are
running, issue the following commands (PID is a process ID returned by
the ps command):
/usr/bin/ps -ef | /usr/bin/grep rpc.statd
/usr/bin/kill -SIGUSR2 PID
/usr/bin/ps -ef | /usr/bin/grep rpc.lockd
/usr/bin/kill -SIGUSR2 PID
The SIGUSR2 signal sets the logging to level 3 (the most detailed level).
The logging for rpc.statd is appended to the file
/var/adm/rpc.statd.log. The logging for rpc.lockd is appended to
the file /var/adm/rpc.lockd.log.
To stop detailed logging of rpc.statd and rpc.lockd, issue the same
commands listed above to send the SIGUSR2 signal to the processes. The
SIGUSR2 signal is a toggle that turns logging on or off, depending on its
current state.
For more information, type man 1M statd or man 1M lockd at the
HP-UX prompt.