pcp
[Top] [All Lists]

Re: [pcp] A number of pmlogger_check gripes ...

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] A number of pmlogger_check gripes ...
From: Chandana De Silva <chandana@xxxxxxxxxxxxx>
Date: Sun, 07 Jul 2013 08:20:30 +1000
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <mailman.1.1373130002.29908.pcp@xxxxxxxxxxx>
References: <mailman.1.1373130002.29908.pcp@xxxxxxxxxxx>
Reply-to: chandana@xxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
Another possible wrinkle is that the pmlogger configs can be either $PCP_SYSCONF_DIR/pmlogger/ or $PCP_LOG_DIR/pmlogger/hostname. So the pmlogger_check needs to look in both places before deciding to do something..

On 07/07/13 03:00, pcp-request@xxxxxxxxxxx wrote:
Fairly straight forward to resolve this - if we add a flag to pmlogconf to
run it in non-interactive, auto-generate/refresh mode.  This can add a new
comment line near the top of the file indicating date/time (pmieconf has
this already, IIRC) of the run, and indicating the fact that it was indeed
auto-generated.  Without that tag, we should leave well alone.  We do leave
well alone non-pmieconf generated configs already, but this was a wrinkle
that I completely didn't anticipate.

I'll need to navel gaze for awhile to ponder whether pmieconf/pmie_check
has had the same problem (for many years).

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [pcp] A number of pmlogger_check gripes ..., Chandana De Silva <=