As a result boot.log file on my CentOS system gets these:
Jul 19 15:57:03 miller crmd: [30496]: info: log_data_element:
build_operation_update: digest:source <parameters
configfile="/etc/httpd/conf/httpd-prod.conf"
statusurl="http://208.30.71.106/server-status"/>
Jul 19 15:57:05 miller crmd: [30496]: info: do_lrm_rsc_op: Performing
op=PROD:Apache_monitor_30000
key=23:17:3d8a8a1c-0607-4930-a01a-da9337405a9e)
Jul 19 15:57:05 miller crmd: [30496]: info: do_lrm_rsc_op: Performing
op=PRODGroup:MailTo_start_0
key=25:17:3d8a8a1c-0607-4930-a01a-da9337405a9e)
Jul 19 15:57:05 miller crmd: [30496]: info: process_lrm_event: LRM
operation PRODGroup:MailTo_start_0 (call=12, rc=0) complete
Jul 19 15:57:05 miller crmd: [30496]: info: build_operation_update:
Digest for 0:0;25:17:3d8a8a1c-0607-4930-a01a-da9337405a9e
(PRODGroup:MailTo_start_0) was 059fa5537db8fb6e537fe4baf5e20ecb
Jul 19 15:57:05 miller crmd: [30496]: info: log_data_element:
build_operation_update: digest:source <parameters
email="[EMAIL PROTECTED]"/>
Jul 19 15:57:05 miller crmd: [30496]: info: process_lrm_event: LRM
operation PROD:Apache_monitor_30000 (call=11, rc=0) complete
Jul 19 16:05:00 miller cib: [30492]: info: cib_stats: Processed 64
operations (937.00us average, 0% utilization) in the last 10min
logfacility feature in ha.cf is commented out.
On 7/19/07, Serge Dubrouski <[EMAIL PROTECTED]> wrote:
Just found that Heartbeat code explicitly uses LOCAL7 logfacility for
system logging:
cl_log_set_entity(entity);
cl_log_set_facility(LOG_LOCAL7);
and so on.
On standard Linux distribution ( RedHat at least) LOCAL7 is dedicated
for boot processes and is directed to go to boot.log. What was the
reason in ignoring the logfacility value from ha.cf and explicitly
using LOCAL7?
--
Serge Dubrouski.
--
Serge Dubrouski.
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
