Installation guide

116 Chapter 6:Network File Sharing Services
– Forced unmount — As part of the mount information, you will be prompted as to whether
forced unmount should be enabled or not. When forced unmount is enabled, if any applications
running on the cluster server have the designated filesystem mounted when the service is being
disabled or relocated, then that application will be killed off to allow the unmount to proceed.
• Export Information — this information is required for NFS services only. If you are only per-
forming file serving to Windows based clients, answer no when prompted regarding NFS exports.
Alternatively, you can configure a service to perform heterogeneous file serving by designating
both NFS exports parameters and the Samba share parameter.
• Samba Share Name — In the process of configuring a service you will be asked if you wish
to share the filesystem to Windows clients. If you answer yes to this question, you will
then be prompted for the Samba share name. Based on the name you specify here, there
will be a corresponding /etc/samba/smb.conf.
sharename file and lock directory
/var/cache/samba/
sharename . By convention the actual Windows share name specified
within the smb.conf.
sharename
will be set in accordance with this parameter. In practice,
you can designate more than one Samba share within an individual smb.conf.
sharename
file. There can be at most 1 samba configuration specified per service; which must be specified
with the first device. For example, if you have multiple disk devices (and corresponding file
system mounts) within a single service, then specify a single sharename for the service. Then
within the /etc/samab/smb.conf.
sharename file, designate multiple individual samba
shares to share directories from the multiple devices. To disable samba sharing of a service, the
share name should be set to
None.
When running the cluadmin utility to configure Samba services:
• Please take care that you correctly enter the service parameters. The validation logic associated
with Samba parameters is currently not very robust.
• In response to most of the prompts, you can enter the
[?] character to obtain descriptive help text.
• After configuring a Samba service via cluadmin, remember to tune the
/etc/samba/smb.conf.
sharename file for each service in accordance with the clients
and authorization scheme you desire.
• Remember to copy the smb.conf.
sharename file over to the other cluster member.
• Perform the recommended step to create the Samba daemon’s lock directory on the other cluster
member, for example: mkdir /var/cache/samba/
acct .
• If you delete a Samba service, be sure to manually remove the
/etc/samba/smb.conf/
sharename file. The cluadmin utility does not automatically
delete this file in order to preserve your site specific configuration parameters for possible
later usage.