HP-UX HB v13.00 Ch-20 - CIFS

HP-UX Handbook Rev 13.00 Page 16 (of 40)
Chapter 20 CIFS
October 29, 2013
usable by the system.
Debugging
To enable an enhanced logging you need to edit /etc/opt/cifsclient/cifsclient.cfg.
Remove slashes before the statement you want to get more information about. The changes will
become active as soon as you close the file. A restart of the cifsclient is not needed. Logfiles will
be found in /var/opt/cifsclient/debug the naming convention is cifsclient-log.pid.
# The following section defines the logging verbosity. All possible levels
# of logging are given, most of them are remarked.
logLevels = (
info,
error,
// debug,
// resource,
netbiosError,
// netbiosDebug,
// netbiosTrace,
// nfsTrace,
// rare,
// cacheDebug,
// cifsTrace,
// oplock,
warn,
// smbSequence,
// debugAttributes,
// debugSSL,
)
If the cifsclient cores then the core files are below /var/opt/cifsclient/core. A file
cifsclientCoreFileInfo to document the cores is there too. It as well documents if a starting
cifsclient renamed one of the core-files these are then called core.renamed.by.pid.
Cifsclient may result in communication difficulties with server that implemented their own
cifsprotocol. We know about some difficulties with "DELL PowerVault NAS 740 N", "EMC
celerra"; "USS (Unix System Services) of OS/390" and "Network Appliance". Note that these
servers are not in the tested list and therefore not supported. If we encounter a problem that is
caused by us we will take care to find a fix, but if it is a protocol error of the server we have no
influence to this.
CIFS client at one glance
Info commands
Info Command
Options
cifslist
-A
M, -U
-s <server>
u <server>
-m <share>