Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ocf_heartbeat_edir88(7) [debian man page]

OCF_HEARTBEAT_EDIR88(7) 					OCF resource agents					   OCF_HEARTBEAT_EDIR88(7)

NAME
ocf_heartbeat_eDir88 - Manages a Novell eDirectory directory server SYNOPSIS
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 configuration 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. SUPPORTED PARAMETERS
eDir_config_file Path to configuration file for eDirectory instance. (unique, optional, string, default /etc/opt/novell/eDirectory/conf/nds.conf) eDir_monitor_ldap Should we monitor if LDAP is running for the eDirectory instance? (optional, boolean, default 0) eDir_monitor_idm Should we monitor if IDM is running for the eDirectory instance? (optional, boolean, default 0) eDir_jvm_initial_heap Value for the DHOST_INITIAL_HEAP java environment variable. If unset, java defaults will be used. (optional, integer, no default) eDir_jvm_max_heap Value for the DHOST_MAX_HEAP java environment variable. If unset, java defaults will be used. (optional, integer, no default) eDir_jvm_options Value for the DHOST_OPTIONS java environment variable. If unset, original values will be used. (optional, string, no default) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 600. stop Stops the resource. Suggested minimum timeout: 600. monitor Performs a detailed status check. Suggested minimum timeout: 60. Suggested interval: 30. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a eDir88 resource using the crm(8) shell: primitive p_eDir88 ocf:heartbeat:eDir88 op monitor timeout="60" interval="30" SEE ALSO
http://www.linux-ha.org/wiki/eDir88_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_EDIR88(7)

Check Out this Related Man Page

OCF_HEARTBEAT_DUMMY(7)						OCF resource agents					    OCF_HEARTBEAT_DUMMY(7)

NAME
ocf_heartbeat_Dummy - Example stateless resource agent SYNOPSIS
Dummy [start | stop | monitor | migrate_to | migrate_from | meta-data | validate-all] DESCRIPTION
This is a Dummy Resource Agent. It does absolutely nothing except keep track of whether its running or not. Its purpose in life is for testing and to serve as a template for RA writers. NB: Please pay attention to the timeouts specified in the actions section below. They should be meaningful for the kind of resource the agent manages. They should be the minimum advised timeouts, but they shouldn't/cannot cover _all_ possible resource instances. So, try to be neither overly generous nor too stingy, but moderate. The minimum timeouts should never be below 10 seconds. SUPPORTED PARAMETERS
state Location to store the resource state in. (unique, optional, string, default /var/run/resource-agents/Dummy-default.state) fake Fake attribute that can be changed to cause a reload (optional, string, default dummy) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 20. stop Stops the resource. Suggested minimum timeout: 20. monitor Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10. reload Suggested minimum timeout: 20. migrate_to Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 20. migrate_from Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 20. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 20. EXAMPLE
The following is an example configuration for a Dummy resource using the crm(8) shell: primitive p_Dummy ocf:heartbeat:Dummy meta allow-migrate="true" op monitor timeout="20" interval="10" depth="0" SEE ALSO
http://www.linux-ha.org/wiki/Dummy_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_DUMMY(7)
Man Page