HP CIFS Server 3.0f Administrator's Guide verison A.02.03

Winbind makes use of several files winbindd.pid, winbindd_cache.tdb, winbindd_idmap.tdb, and
directory winbindd_privileged, in the /var/opt/samba/locks directory.
You may want to put the entire /var/opt/samba/locks directory on a logical shared volume but the
locking data may not be correctly interpreted after a failover. You may want to add a line to your
startup script to remove the locking data file .../locks/locking.tdb.
• Samba as a WINS Server
If you configure your Samba server to be a WINS server by setting the wins support parameter to
yes, it will store the WINS database in the file /var/opt/samba/locks/WINS.DAT .
If this file is not on a logical shared volume, when a failover occurs, there will be a short period of time
when all the WINS clients update the Samba WINS server with their address. However, if this short
period of time to restore the WINS database is not acceptable, you can reduce the period of time to
restore the full WINS service.
To do so, configure /var/opt/samba/locks/WINS.DAT to be a symbolic link to a WINS.DAT file on
a logical shared volume. HP does not recommend putting the entire /var/opt/samba/locks directory
on a logical shared volume, because the locking data may not be correctly interpreted after a failover.
• Samba as a Master Browser
If you configure your Samba server to be the domain master browser by setting the domain master to
yes, it will store the browsing database in the /var/opt/samba/locks/browse.tdb file. HP does not
recommend doing this in an HA configuration.
If you do so, you will probably want to configure /var/opt/samba/locks/browse.tdb as a symbolic
link to a BROWSE.DAT file on a logical shared volume. HP doesn't recommend putting the entire
/var/opt/samba/locks directory on a logical shared volume because the locking data may not be
correctly interpreted after a failover. You may want to add a line to your startup script to remove the
locking data file, /locks/locking.tdb .
• Automatic Printer Sharing
If you configure your Samba server with a [printers] share to automatically share all the printers
on your HP-UX system, then you will need to be certain that all your MC/ServiceGuard nodes have the
same HP-UX printers defined. Otherwise, when a failover occurs, the list of shared printers for the
Samba server will change, resulting in problems on clients using those printers.
• Samba's LMHOSTS File
If you wish to use an LMHOSTS file to store the static addresses for certain netbios names, HP
recommends that you put the LMHOSTS file on a logical shared volume. To do this you will need to
specify a different path for the LMHOSTS file using the -H option when invoking nmbd . HP recommends
that you put the LMHOSTS file on a logical shared volume so that all the nodes can share it.
You will need to edit the MC/ServiceGuard scripts to add the -H options to the places where nmbd is
invoked directly. You will also need to edit the /opt/samba/bin/startsmb script to add the -H option
to the places where nmbd is started.
• Utilities
In the MC/SG cluster environment, some utilities need to specify the location of the smb.conf file for
the package. For example:
smbpasswd -c /etc/opt/samba/pkg1/smb.conf.pkg1 -a username
smbclient -s /etc/opt/samba/pkg1/smb.conf.pkg1 //ha_server1/lvm1a -c ls
testparm -s /etc/opt/samba/pkg1/smb.conf.pkg1
smbstatus -s /etc/opt/samba/pkg1/smb.conf.pkg1
• Network File System (NFS) and Veritas Cluster File System (CFS)
NFS and Veritas CFS permits concurrent file access from multiple nodes. Since most file locking
mechanisms do not span across multiple systems, you should use extra caution when configuring CIFS
Server in an NFS or a CFS environment. See Chapter 2, section "Special Concerns when Using HP
CIFS Server with a Network File System (NFS) or a Clustered File System (CFS)".
162 Configuring HA HP CIFS