HP CIFS Client A.02.02.03 Release Notes

Known Problems and Workarounds
This section provides a list of known problems and workrounds as known to HP at time of
publication.
For the HP CIFS Client
• Byte range lock is not supported
Byte range locks over a cifs mount are not supported. Calls to lockf(1) and fcntl(1)
over a cifsmount will fail. Support for byte range locks will be added in a future release of
the HP CIFS Client.
• Removing a Directory and its Contents
Removing a directory and its contents in one step using the command, rm -rf
<directory>, may fail on directories located on a cifsmount. If the directory contains
~30 or more files, only part of the directory contents will be removed and the directory itself
will remain since its contents have not been removed.
A workaround is to remove the directory and its contents in two steps as follows:
1. rm —rf <dir>/*
2. rmdir <dir>
• NetBIOS names with non-alphanumeric characters, in configuration file, must be quoted
In instances where an “individual server” is defined in the CIFS Client configuration file
(/etc/opt/cifsclient/cifsclient.cfg), and the server's NetBIOS name contains a
non-alphanumeric character, unexpected behavior can occur if the name is not enclosed in
quotes. The proper form is shown in this example of a server name that contains a hyphen:
"server-a" = {
parameter = value;
...etc... };
Individual-server definitions allow system administrators to configure non-default values for
particular servers. Examples are given in the discussion of “SMB over TCP” in the Configuration
File chapter of the HP CIFS Client Administrator's Guide, and at the end of the configuration
file itself.
• CIFS Client uses PAM Kerberos authentication to connect to a CIFS server
When Kerberos authentication has been configured and the user has logged into the CIFS
Client HP-UX host with a Ticket-Granting Ticket (TGT) in the system Kerberos credentials cache,
established with PAM Kerberos, the user can not perform an automatic login (cd, ls, etc)
to access a CIFS mount point directly. Without an explicit login, the user gets the
ACCESS_DENIED error when attempting to access a CIFS client mount point.
This known problem is that PAM Kerberos sets the KRB5CCNAME environment variable to
/tmp/krb5cc_{ppid}_{pid} when initializing the user session. The CIFS Client daemon
has no current provision to get the Kerberos credentials cache path from the KRB5CCNAME
environment variable. The CIFS Client daemon requires that the system Kerberos cache with
a pre-existing TGT to be found in the default file location, /tmp/krb5cc_{uid}.
To automatically login and gain access to the CIFS share from the PAM Kerberos authenticated
session using an existing credential stored in the system Kerberos cache, use the following
workaround:
1. Use a script to link the system Kerberos cache file established by PAM Kerberos to the
default file location, /tmp/krb5cc_{uid}. The following is a sample script:
#!/usr/bin/sh
# If you do not use Kerberos authentication, you do not need to use this script.
# You must call this script as part of your .profile script on all the
# HP-UX systems that use the HP CIFS Client with Kerberos authentication# and KRB5-PAM module.
# You may pass the letter "d" as a parameter to this script to debug the script.
# Link the Kerberos credential cache created by PAM Kerberos to the
# default file path /tmp/krb5cc_{uid} which can be read by the HP CIFS Client.
Known Problems and Workarounds 9