Installation guide

Section 6.2:Setting Up a High Availability Samba Service 119
relocate: yes
user script: None
monitor interval: 90
IP address 0: 10.0.0.10
netmask 0: None
broadcast 0: None
device 0: /dev/sdb12
mount point, device 0: /mnt/users/accounting
mount fstype, device 0: ext2
mount options, device 0: rw,nosuid,sync
force unmount, device 0: yes
samba share, device 0: acct
Add samba_acct service as shown? (yes/no/?) yes
After running cluadmin as shown above to configure the service, remember to:
• Customize /etc/samba/smb.conf.
sharename accordingly.
• Copy /etc/samba/smb.conf.
sharename over to the other cluster member.
• Create the suggested lock directory on the other cluster member, e.g. mkdir
/var/cache/samba/
acct
6.2.5 smb.conf. sharename File Fields
This section describes the fields within the smb.conf. sharename file which are most relevant to
the correct operation of highly available Samba services. It is beyond the scope of this document to
completely describe all of the fields within a Samba configuration file. There have been no additional
field names added in support of clustering, and the file format follows the normal Samba conventions.
Shown below is an example smb.conf.
sharename file which was automatically generated by
cluadmin in response to the service specific parameters. This example file matches the above clu-
admin service configuration example.
# Template samba service configuration file - please modify to specify
# subdirectories and client access permissions.
# Remember to copy this file over to other cluster member, and create
# the daemon lock directory /var/cache/samba/acct.
#
# From a cluster perspective, the key fields are:
# lock directory - must be unique per samba service.
# bind interfaces only - must be present set to yes.
# interfaces - must be set to service floating IP address.
# path - must be the service mountpoint or subdirectory thereof.
# Refer to the cluster documentation for details.
[global]