On Thu, Apr 15, 2010 at 7:22 PM, Alan Jones wrote:
> On Wed, Apr 7, 2010 at 6:38 AM, Andrew Beekhof wrote:
>>
>> > It seems there are only two configuration options for pacemaker as
>> > started
>> > by
>> > corosync: use_logd which I've enabled and use_mgmtd which I don't
>> > understand.
>>
>>
On Wed, Apr 7, 2010 at 6:38 AM, Andrew Beekhof wrote:
> > It seems there are only two configuration options for pacemaker as
> started
> > by
> > corosync: use_logd which I've enabled and use_mgmtd which I don't
> > understand.
>
> pacemaker also uses the logging options of corosync.conf
> though
On Fri, Apr 2, 2010 at 1:03 AM, Alan Jones wrote:
> Hi,
> I would like to set debugging levels higher than zero with
> pacemaker/corosync.
>
> [r...@fc12-a heartbeat]# ./crmd version
> CRM Version: 1.0.5 (ee19d8e83c2a5d45988f1cee36d334a631d84fc7)
> [r...@fc12-a heartbeat]# corosync -v
> Corosync C
This worked. Let me know if there is a better way. From crm.h:
#ifdef ALAN_JONES_WANTS_HIS_LOG_MESSAGES
#define do_crm_log_unlikely(level, fmt, args...) do { \
if(__likely(crm_log_level < (level))) { \
continue;
Hi,
I would like to set debugging levels higher than zero with
pacemaker/corosync.
[r...@fc12-a heartbeat]# ./crmd version
CRM Version: 1.0.5 (ee19d8e83c2a5d45988f1cee36d334a631d84fc7)
[r...@fc12-a heartbeat]# corosync -v
Corosync Cluster Engine, version '1.1.2' SVN revision '2539'
Copyright (c) 2
