HP CIFS Client A.02.02.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents HP CIFS Client Overview...........................................................................................................4 Problems Fixed in Version A.02.02.03.........................................................................................4 Configuration Parameter Changes...............................................................................................4 Compatibility and Installation Requirements.........................................................................
HP CIFS Client Overview CIFS is the native networking protocol on Microsoft Windows operating systems. The HP CIFS products for HP-UX provide a wide range of integration strategies for HP-UX and Windows.
This boolean variable works in conjunction with "useUnicode". useStrictUnicode ensures that Unicode is strictly used in all communication. By default it is set to no. Compatibility and Installation Requirements This section describes the compatibility information and hardware requirements for this release. Hardware Requirements This version of HP CIFS Client runs on the following hardware: • HP 9000 computers • HP Integrity computers Operating System Requirements HP CIFS Client A.02.02.
Changes and Fixes in Previous Release Problems Fixed in Version A.02.02.02 HP CIFS Client A.02.02.02 is a maintenance release. Users are encouraged to upgrade to this version, several defects have been fixed, and few changes have been made, as described below. HP CIFS Client A.02.02.02 provides the following fixes. For detailed information about few changed features, see “New or Changed Features in Version A.02.02.02” section.
New or Changed Features in Version A.02.02.02 This release contains the following changes: • Logins to HP-UX systems via secure shell (ssh) now supported by PAM-NTLM (JAGag18827) The PAM-NTLM software provided in the CIFS Client bundle has been enhanced to support HP-UX login requests that use the ssh protocol. • README file updated The README file in /opt/cifsclient has been revised, a brief introduction to the product has replaced outdated text. Changes in A.02.02.
sockMode, sockOwner, sockGroup These parameters pertain to the UNIX permissions of the socket on which the CIFS Client daemon listens for requests from CIFS Client commands (mount -F cifs, cifsmount, cifslist, etc). The default values of these parameters should not been changed, hence their values are no longer read from the configuration file. The values are sockMode = 0666, sockOwner = root, sockGroup = root. Fixes in A.02.02.01 Release The following fixes are included in the previous A.02.02.
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.
if [[ $KRB5CCNAME != "" ]] then echo $KRB5CCNAME | read krb5ccname if [[ $1 = 'd' ]] then print "KRB5CCNAME="$KRB5CCNAME fi print $KRB5CCNAME | sed -e s'/_/ /' | read p1 p2 print $p2 | sed -e s'/_/ /' | read ppid pid id | read i1 i2 if [[ $1 = 'd' ]] then print "ppid & pid = ["$ppid"] ["$pid"]" fi print $i1 | sed -e s'/=/ /' | sed -e s'/(/ /' | read u1 uid u3 if [[ $1 = 'd' ]] then print "uid=["$uid"]" fi fname="/tmp/krb5cc_${uid}" # Remove the cifs client's link file that already exists.
clientCharMapFile, which selects any one of the many character mapping files provided with the product. Character translations for communications with CIFS Servers can be done either in Unicode or through the configuration parameter serverCharMapFile, which also is used to select a character mapping file. Use of Unicode is turned on and off with the useUnicode parameter.