use_logd - the directive to determine whether heartbeats use logging daemon or not

The use_logd directive specifies whether Heartbeat[1] logs its messages through logging daemon or not. The syntax is simple:

use_logd <on/off>

(Note: use_logd can be any HeartbeatBoolean[2] value)

The detailed policy is:

1. if there is any entry for debugfile[3]/logfile[4]/logfacility[5] in ha.cf[6]

• a) if use_logd is not set, logging daemon will not be used

  b) if use_logd is set to on, logging daemon will be used

  c) if use_logd is set to off, logging daemon will not be used

2. if there is no entry for debugfile[3]/logfile[4]/logfacility[5] in ha.cf[6]

• a) if use_logd is not set, logging daemon will be used

  b) if use_logd is set to on, logging daemon will be used

  c) if use_logd is set to off, config error, i.e. you can not turn off all logging options

If the logging daemon is used, all log messages will be sent through IPC to the logging daemon, which then writes them into log files. In case the logging daemon dies (for whatever reason), a warning message will be logged and all messages will be written to log files directly.

If the logging daemon is used, logfile[4]/debugfile[3]/logfacility[5] in this file are not meaningful any longer. You should check the config file for logging daemon (the default is /etc/logd.cf).

If use_logd is not used, all log messages will be written to log files directly.

The logging daemon is started/stopped in heartbeat script.

Setting use_logd to "yes" is recommended.

---

This information provided courtesy of the Linux-HA project at http://linux-ha.org/