Novell SUSE LINUX ENTERPRISE SERVER 10 SP2 HEARTBEAT Manual page 127

ocf:eDir88 (7)
ocf:eDir88 — eDirectory resource agent
Synopsis
OCF_RESKEY_eDir_config_file=string
[OCF_RESKEY_eDir_monitor_ldap=boolean]
[OCF_RESKEY_eDir_monitor_idm=boolean]
[OCF_RESKEY_eDir_jvm_initial_heap=integer]
[OCF_RESKEY_eDir_jvm_max_heap=integer]
[OCF_RESKEY_eDir_jvm_options=string] eDir88 [start | stop | monitor | meta-
data | validate-all]
Description
Resource script for managing an eDirectory instance. Manages a single instance of
eDirectory as an HA resource. The "multiple instances" feature or eDirectory has been
added in version 8.8. This script will not work for any version of eDirectory prior to
8.8. This RA can be used to load multiple eDirectory instances on the same host. It is
very strongly recommended to put eDir configuration files (as per the eDir_config_file
parameter) on local storage on each node. This is necessary for this RA to be able to
handle situations where the shared storage has become unavailable. If the eDir configu-
ration file is not available, this RA will fail, and heartbeat will be unable to manage the
resource. Side effects include STONITH actions, unmanageable resources, etc... Setting
a high action timeout value is _very_ _strongly_ recommended. eDir with IDM can
take in excess of 10 minutes to start. If heartbeat times out before eDir has had a chance
to start properly, mayhem _WILL ENSUE_. The LDAP module seems to be one of the
very last to start. So this script will take even longer to start on installations with IDM
and LDAP if the monitoring of IDM and/or LDAP is enabled, as the start command
will wait for IDM and LDAP to be available.
HB OCF Agents 119