pcp
[Top] [All Lists]

Re: [pcp] Another Possible Fresh Install Problem

To: Dave Brolley <brolley@xxxxxxxxxx>
Subject: Re: [pcp] Another Possible Fresh Install Problem
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Sun, 2 Feb 2014 20:56:53 -0500 (EST)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <52EBC1AF.3040107@xxxxxxxxxx>
References: <52EBC1AF.3040107@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: HPLXLqsvrZnSen2nrqshBEa207u+Aw==
Thread-topic: Another Possible Fresh Install Problem

----- Original Message -----
> Got this while running qa test 646 as part of the 'sanity' group on my
> new workstation. ANother possible fresh install problem?
> 
>  > mmv_stats_init failed : No such file or directory
>  > mmv_stats_init failed : No such file or directory
>  > /var/lib/pcp/tmp/mmv/test21668: No such file or directory
>  > /var/lib/pcp/tmp/mmv/notest21668: No such file or directory
> 

This is a QA test failure - a few releases back we made a change
to no longer enforce the security policy for the mmv directory.
We now make it opt-in for new installs, so that the user chooses
how they wish to setup the pmdammv <-> client communication, and
can choose a more security-restrictive channel if they desire.

For upgrades, the situation is that the pre-existing situation
(where the pcp package installed a world-writable-sticky-bit-set
directory for instrumented apps) continues on unchanged - hence,
I'd not tripped over this yet. :)

I'll fix up the test - thanks Dave.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [pcp] Another Possible Fresh Install Problem, Nathan Scott <=