Re: [pcp] pcp updates: QA for pmlogger - handle stale primary control and socket files

[Mark Goodwin <mgoodwin@xxxxxxxxxx>]

On 07/29/2015 05:29 PM, Nathan Scott wrote:
> Hi Mark,
>
> ----- Original Message -----
> > new qa/808 will fail unless you have the earlier commit, see below.
> >
> > Changes committed to git://pcp.io/markgw/pcp/pcp.git master
>
> I pushed some fixes to 280 and 430 that are related today - and those
thanks

> made me wonder about the upgrade scenario.  Could you test the case
> where we have a primary logger running from an older PCP (hardlink'd)
> and upgrade?  Its not clear if that process will go smoothly now.
yes good point - I'll test it. I suspect the solution will be a %postun
scriptlet in the RPM spec to remove all pmlogger control files and sockets
and links thereto, whether hard links or soft. But that assumes we'll always
want to restart pmlogger services after an upgrade; is that reasonable?
(and ditto similar for Deb upgrades).

Cheers