----- Original Message -----
> ...
> As Dave noted later, and I discovered independently, making
> /var/lib/pcp/config/pmda owned by the user pcp appears to be sufficient
> for most cases.
>
> The simple PMDA seems to be the main culprit, so I also applied an Irish
> (to be sure, to be sure) fix to the Install script there to remove any
> of its own PMDA InDom files from this directory before starting a new
> invocation of the PMDA.
For some unfathomable reason, when Dave mentioned it to me I thought it
was just pmdasimple affected, but of course its indicative of a slightly
wider problem.
> The one problem with all of this is that /var/lib/pcp/config/pmda is not
> actually included in the PCP package ...
I think we have to do this now right? And I think, given a PMDA can now
run as any user (well, always could, so this problem has always existed),
we need to make it another tmpdir-alike (sticky bit set) directory ... ?
On top of that, the Install chown trick sounds like the way to go. We're
a bit fortunate I guess that more PMDAs are not using this (pmdapostgres,
etc) so far, with their own user accounts - that would've compounded the
issue a fair bit.
cheers.
--
Nathan
|