All other sections in the configuration file define the file and/or print shares that clients can attempt to access for this instance. A configuration file must have one or more shares defined. The Samba configuration file can contain file shares only, print shares only or a combination of both file and print shares. LifeKeeper does not limit the number of shares that can be defined, but one must realize that a failure relating to any one share could cause the entire hierarchy to be switched over to the backup server. The following directives must be defined for each share:
- path – This directive identifies the pathname at the root of the file or print share. The value determines the File System resource to be protected as part of the Samba hierarchy. If the LifeKeeper File System resource does not already exist when the Samba resource is created, LifeKeeper will create it for you.
Note: This directive is sometimes called directory. The recovery kit will handle both directive names.
- printable – A Yes value indicates that the Samba share is used as a print spool repository for printing to Linux printers. If the share is to be a regular file share then set this directive to No or do not specify it, as it is No by default unless set to Yes in the [global] section. If this directive is set to Yes, then creation of a Samba hierarchy will require the existence of LifeKeeper Print Services resource that protects the printer defined via the printer name directive listed below.
Note:This directive is sometimes called print ok. The recovery kit will handle both directive names.
- printer name – This directive defines the printer name used by the share and is used to find a Print Services instance that protects the named printer. The Print Services instance will become a child resource in the Samba hierarchy. If this directive is not defined for a printer share, the Samba Recovery Kit will use the share name as the printer name.
Note: This directive is sometimes called printer. The kit will handle both directive names.