----- Original Message -----
> On 15/07/13 12:51, Nathan Scott wrote:
> > Hi Ken,
> > ...
> > Given other follow-up mail, could the reverse of what you wrote
> > above have happened (no PCP_SYSCONF_DIR file initially)? Or,
> > could you be a victim of the PCP_VAR_DIR/pmlogger/config ->
> > PCP_SYSCONF_DIR transition? (if so, this issue would have had
> > nothing to do with the pmlogconf changes at all!).
>
> On reflection, your second explanation above is most likely.
>
> This was an older PCP installation (predates the move to
> $PCP_SYSCONF_DIR) and I hand installed just the pmlogger_* scripts [yes
> I know about the cardinal rules of not doing this], but I was out of
> options to find a testbed to check my fix for
> http://oss.sgi.com/bugzilla/show_bug.cgi?id=979
>
> I did review the diffs in the scripts, but amongst all the differences I
> checked I totally missed the PCP_VAR_DIR/pmlogger/config -> PCP_SYSCONF_DIR.
>
> Apologies for the grief.
No problem at all - it was a timely reminder to take extra care when
we are working in this area!
It made me reminisce about the occasional puppet-driven update I have
seen, pushing changes out to hundreds of machines, and shortly alarms
start going off on the first few ... oh, that sinking feeling! ;)
cheers.
--
Nathan
|