Serge Dubrouski wrote:
> 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?
With regard to ha.cf:
logfacility is now controlled (according to our recommended
practice) by the logging daemon config file
With respect to the statements you mentioned, this definitely some kind
of weirdness. In the utilities, and the test program, it's about
half-understandable. The system has a well-defined set of logging
methods, and ways of inheriting logging information - and this isn't it.
You should be running the logging daemon. I think then this might not
happen (but I'm not sure).
--
Alan Robertson <[EMAIL PROTECTED]>
"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
