Sounds like an accidental regression - any ideas so far Ken?, else I'll queue
it up for further investigation here.
thanks.
----- Original Message -----
> Hi,
> I am trying to track down some strangeness I'm seeing in pmlogger
> configuration between 3.10.0 and recent git.
>
> On a 3.10.0 system i have the following in /etc/pcp/pmlogger/control. All
> defaults except the primary logger line:
>
> ####
> LOCALHOSTNAME y n PCP_LOG_DIR/pmlogger/LOCALHOSTNAME -r -c primary.logger
> ####
>
> The file:
>
> /etc/pcp/pmlogger/primary.logger
>
> exists and everything works as expected.
>
>
> On a recent git system, with the same config, pmlogger does not find the
> primary.logger file and seems to construct a new (unrelated) one with
> pmlogconf in /var/lib/pcp/config/pmlogger/primary.logger that appears to be
> some sort of default config on startup.
>
> The change seems to come from here:
>
> 0020568401cefe9df692e2f705b8133a8ab87f0d
>
> I guess I have 2 questions:
>
> 1. The comment led me to believe that everything should still work since it
> says "." is searched first and I would expect "." to map to
> /etc/pcp/pmlogger since that is where the control file lives. Is that not
> correct?
>
> 2. This was on a clean install with rpms built from git on a Centos 6.5
> machine. I can deal with this on new systems by putting the config in the
> right place, but what is the expected behavior on upgrade? I am setting up a
> test system that I can upgrade shortly, because I got lost in the config
> file logic in the spec file, and am not sure if the right thing will happen
> in terms of moving existing config files to the new right place.
>
> Thanks
>
> Martins
>
>
>
>
>
>
>
>
>
> _______________________________________________
> pcp mailing list
> pcp@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/pcp
>
|