On 5/22/12 3:33 AM, Andrew Beekhof wrote:
and I see nothing in
> pacemaker itself that gives me any separate controls over its logging
> verbosity.
Which is why I mentioned:
>>
>> You should be able to define
>> PCMK_trace_functions=nction1,function2,... as an environment
There is also PCMK_trace_files.
Depending on your version you may also be able to set
PCMK_debug=crmd,pengine,... or send SIGUSR1 to the process to increase
the log level
>>
>> variable to get additional information from just those functions.
>> It might take a bit of searching through source code to find the ones
>> you care about, but it is possible.
Thanks! I actually have a couple of different versions I am dealing with. I will poke through the
source for the newest one (SLES11 SP2 ... pacemaker 1.1.6) I have and see what I can do. I actually
do not have a specific problem I am tracking right now. I am just trying to develop a tool kit of
things to do when one of our customers runs into resource issues.
--
Ron Kerry rke...@sgi.com
Global Product Support - SGI Federal
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
