Re: [pcp] patch/RFC - install global derived metrics dir and configs

[Ken McDonell <kenj@xxxxxxxxxxxxxxxx>]

On 11/03/16 08:29, Mark Goodwin wrote:
> ...
> yes, but 2. and 4. are also available, as follows :
>
> 2.
> PCP_DERIVED_CONFIG=/var/lib/pcp/config/derived:/my/own/private:/some/where/else
>
>
> 4. PCP_DERIVED_CONFIG=""
>
> The current patchset actually checks access($PCP_CONFIG_DERIVED, F_OK)
> which is not
> appropriate for case 2., so I'll fix that.
>
> > we probably need another control variable optionally set in the
> > environment (PCP_NO_DERIVED?) to get the missing 2 behaviours.
> is PCP_DERIVED_CONFIG="" OK for that? It just prevents any config being
> loaded at all (case 4.)
Yep, if the empty string does the job, that's fine.  And the PATH-like 
syntax (that I'd forgotten) for PCP_CONFIG_DERIVED does the job for the 
other case(s).
> > ... what's the rationale for any framework to impose/expect a .d
> > suffix for a directory name?
> just that Frank's earlier reply suggested the directory be called
> "config.d", but OK I've
> perished the thought :P
Good decision!