pcp
[Top] [All Lists]

pcp updates

To: pcp@xxxxxxxxxxx
Subject: pcp updates
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Thu, 26 Nov 2009 10:29:02 +1100
Reply-to: kenj@xxxxxxxxxxxxxxxx
Changes committed to git://oss.sgi.com/kenj/pcp.git dev

 man/man1/pcpintro.1         |   33 ++++++++++++++++++++---
 src/include/impl.h          |    5 ++-
 src/libpcp/src/logconnect.c |   48 ++++++++++++++++++++++++++++++++--
 src/libpcp/src/logcontrol.c |    6 ++--
 src/pmlc/actions.c          |   62 +++++++++++++++++++++++++++++++++++++++-----
 src/pmlc/gram.y             |    8 +++++
 src/pmlc/lex.l              |    1 
 src/pmlc/pmlc.c             |    8 +++++
 src/pmlc/pmlc.h             |    1 
 src/pmlogger/dopdu.c        |   42 +++++++++++++++++++++++++----
 src/pmlogger/logger.h       |    5 +++
 src/pmlogger/pmlogger.c     |    2 +
 12 files changed, 198 insertions(+), 23 deletions(-)

commit 9cc29e2a97ba110d295044c263bbdfa6556ce79d
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date:   Thu Nov 26 10:23:17 2009 +1100

    Add PMLOGGER_REQUEST_TIMEOUT support
    
    Setting $PMLOGGER_REQUEST_TIMEOUT in  the environment defines a number
    of seconds for the timeout to be applied to interactions between pmlc
    and pmlogger ... specifically, pmlc will timeout in a __pmGetPDU call
    if the pmlogger is not responding.
    
    Added __pmLoggerTimeout() to libpcp as checks need to be made in libpcp
    (logconnect.c and logcontrol.c) and in pmlc (mostly in actions.c)
    
    Requested by Nathan after strange failure of pmlogger monitoring
    scripts in their production environment when pmlc connected to a
    morbid pmlogger but the pmlc hung trying to get information from
    pmlogger.


<Prev in Thread] Current Thread [Next in Thread>