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

HP-UX Handbook – Rev 13.00 Page 15 (of 40)
Chapter 20 CIFS
October 29, 2013
HP CIFS Client and WAN
Some configurations require special settings. So we noted that when using cifsclient connections
over a wide area network (e.g. ISDN router) then you might have to adapt some of the
parameters in /etc/opt/cifsclient/cifsclient.cfg:
//nfsTransferSize = 8192; // unchanged !
connectTimeout = 5000 // timeout for netbios connection in ms
requestTimeout = 40000 // timeout for SMB reply in ms
nfsTimeout = 600 // initial nfs timeout in 1/10 seconds
nfsRetransmit = 8 // number of nfs retransmissions
HP CIFS Client and permanent mounts (fstab)
Usually HP-UX administrators would write a mount that they want to be initialised at boot time
into the /etc/fstab, which is processed during system startup. During that time cifsclientd is
not yet running. This means that mounting a smb/cifs-share to a HP-UX-system should be
possible without a manual mount or an entry in the /etc/fstab! HP CIFS client offers a very
nice feature, which holds the connected shares, servers, users and password in a binary database.
This enables cifsclientd to remount each share that was in use after it has been stopped and
restarted. Therefore no /etc/fstab entry is needed. The option to use is -s. The databasefile
containing this info is /var/opt/cifsclient/cifsclient.udb.
root@hp-ux:>cifsmount //NTSERV/public /cifs_mnt -U administrator -P –s
root@hp-ux:>cifslist –A
=========================================================================
server NTSERV:
=========================================================================
Remote Username: administrator Local Username: root
Share: \\NTSERV\PUBLIC
rw /cifs_mnt
So you can see that we're now connected to NTSERV as administrator which is locally handled
as root. We can now check for the existance of the database file we mentioned and check its
contend:
root@hp-ux:>ll /var/opt/cifsclient/cifsclient.udb
-rw------- 1 root sys 244 Jul 11 13:59 /var/opt/cifsclient/cifsclient.udb
root@hp-ux:>cifslist –M
mountpoints in database:
-------------------------------------------------------------------------
Mountpoint Share
Server Name Server IP Port Client Name Local User
-------------------------------------------------------------------------
rw /cifs_mnt \\NTSERV\public NTSERV 139 root
This would survive a cifsclient stop or even a reboot. As cifsclientd connects the servers and
mounts the shares which are in its databasefile. That would finally mean that if you start
cifsclient in runlevel 2 by its startscript it would map all the shares for you, so that they are