Login or Register to Ask a Question and Join Our Community

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_XINETD(7) 					OCF resource agents					   OCF_HEARTBEAT_XINETD(7)

NAME

       ocf_heartbeat_Xinetd - Manages a service of Xinetd

SYNOPSIS

       Xinetd [start | stop | status | monitor | meta-data | validate-all]

DESCRIPTION

       Resource script for Xinetd. It starts/stops services managed by xinetd by enabling or disabling them in the configuration file.

       The xinetd daemon itself must be running: we are not going to start or stop it ourselves.

       All services should have a line saying either "disable=yes" or "disable=no". The script just changes those settings before reloading
       xinetd.

       Important: in case the services managed by the cluster are the only ones enabled, you should specify the -stayalive option for xinetd or it
       will exit on Heartbeat stop. Alternatively, you may enable some internal service such as echo.

SUPPORTED PARAMETERS

       service
	   The name of the service managed by xinetd.

	   (required, string, no default)

SUPPORTED ACTIONS

       This resource agent supports the following actions (operations):

       start
	   Starts the resource. Suggested minimum timeout: 20s.

       stop
	   Stops the resource. Suggested minimum timeout: 20s.

       restart
	   Suggested minimum timeout: 20s.

       status
	   Performs a status check. Suggested minimum timeout: 10. Suggested interval: 10.

       monitor
	   Performs a detailed status check. Suggested minimum timeout: 10. Suggested interval: 10.

       validate-all
	   Performs a validation of the resource configuration. Suggested minimum timeout: 5.

       meta-data
	   Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.

EXAMPLE

       The following is an example configuration for a Xinetd resource using the crm(8) shell:

	   primitive p_Xinetd ocf:heartbeat:Xinetd 
	     params 
	       service=string 
	     op monitor depth="0" timeout="10" interval="10"

SEE ALSO

       http://www.linux-ha.org/wiki/Xinetd_(resource_agent)

AUTHOR

       Linux-HA contributors (see the resource agent source for information about individual authors)

resource-agents UNKNOWN 					    06/09/2014						   OCF_HEARTBEAT_XINETD(7)
Man Page