Just picking up on a short irc exchange from a couple of days ago ...
Now we're certainly out on a limb here ...
kenj@bozo:~/src/pcp/src/pmie$ sudo find /etc ! -user root
/etc/apt-cacher-ng/security.conf
/etc/pcp/pmlogger
/etc/pcp/pmlogger/control
/etc/pcp/pmlogger/config.default
/etc/pcp/pmcd/pmcd.options
/etc/pcp/pmie
/etc/pcp/pmie/control
/etc/pcp/pmie/config.default
/etc/bind/rndc.key
I've done some investigation and have explanations, but no solutions ...
so this is open for discussion.
/etc/pcp/pmie/control and /etc/pcp/pmlogger/control could probably be
changed to root.root, mode 644 without anything bad happening.
But /etc/pcp/pmie/config.default and /etc/pcp/pmlogger/config.default
are messier. These do not (and cannot) come from the packaging, they
are created dynamically in one-trip code using pmieconf and pmlogconf
... and in the process of that creation there is a chown pcp:pcp which I
don't think is necessary, but that seems to have triggered the pcp:pcp
ownership of the enclosing directories (again not necessary).
And then there is a bunch of packaging rework to be done ... the pcp.pcp
and mode changes are done in different ways for different packaging models.
And finally, the upgrade path is problematic ... I've run into a number
of totally unexplained oddities in the debian packaging tools when
trying to move from one ownership/mode to another ... I plan to write
this off as a warp in the time-space continuity and move on.
It is likely that this will be tackled in a number of small scope
commits which I'll want to run through a full QA cycle (takes 3 or 4
days), so don't expect anything too soon.
|