HP CIFS Client A.02.02.03 Administrator's Guide

fuser(1M)) or cifsclient fuser [-v] mountpoint command against the given
mountpoint and each of its subdirectories. This is useful for determining which processes are
accessing the mount, in the event that mounting fails with a "device busy" message. Terminate
these processes tied to the mountpoint, then invoke the cifsmount or mount command to succeed.
CIFS Client Log File and Log Levels
The CIFS Client produces a log file of its activities, in the directory
/var/opt/cifsclient/debug. Each time the client starts, it creates a new log file, named
client-log.pid, where pid is the HP-UX process id of the CIFS Client daemon,cifsclientd.
Normally, the log file records only errors or warnings. But, many log levels can be enabled for
checking activities of various modules within the CIFS Client.
If you report a problem to HP, your support representative may ask you to enable one or more log
levels. This is done by editing the CIFS Client configuration file,
/etc/opt/cifsclient/cifsclient.cfg, and uncommenting the particular log level, by
removing the preceding # character and saving the file.
You do not need to restart the CIFS Client for it to recognize the newly enabled (or disabled) log
levels.
Note that increased logging consumes more disk space and slows the performance of the CIFS
Client. Hence, when you do not need logging, it is best to disable it. Refer to the
cifsclient.cfg.default file for recommended default operating log levels.
If a log size reaches 50 Megabytes, it is copied with .prev appended to its name, and a new
log is started. If the new log reaches 50 Megabytes, it is copied with .prev appended, overwriting
the previous one.
46 Troubleshooting and Error Messages