pcp
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [pcp] odd problem in qa/255 for UNIX domain socket for pmcd

from [Ken McDonell] [Permanent Link][Original]
To: Dave Brolley <brolley@xxxxxxxxxx>
Subject: Re: [pcp] odd problem in qa/255 for UNIX domain socket for pmcd
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Sat, 20 Jul 2013 06:29:13 +1000
Cc: "Frank Ch. Eigler" <fche@xxxxxxxxxx>, PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <51E950AC.4000306@xxxxxxxxxx>
References: <51E9186A.4040006@xxxxxxxxxxxxxxxx> <y0mzjtiy6ys.fsf@xxxxxxxx> <51E950AC.4000306@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 
On 20/07/13 00:43, Dave Brolley wrote:

...
We solved this by creating /var/run/pcp as '775 root pcp':

commit f31ccfc82dfe79d444637b132feb71148458408c
Author: Dave Brolley <brolley@xxxxxxxxxx>
Date:   Wed Jul 3 21:19:16 2013 -0400

     Make sure that $PCP_RUN_DIR is insatlled as '775 $PCP_USER
$PCP_GROUP'.


Thanks Dave.
But, ahem, that commit only fixes the problem for RPM based packaging ... the world is a little larger than that.
When these sort of changes are made in the RPM spec files, could we please have a volley of skyrockets and red flag waving so the non-rpm bunnies can make the matching changes for all the other packaging options supported by PCP?
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: pmlogconf including proc metrics?, Frank Ch. Eigler
Next by Date:  Re: [pcp] odd problem in qa/255 for UNIX domain socket for pmcd, Dave Brolley
Previous by Thread:  Re: [pcp] odd problem in qa/255 for UNIX domain socket for pmcd, Dave Brolley
Next by Thread:  Re: [pcp] odd problem in qa/255 for UNIX domain socket for pmcd, Dave Brolley
Indexes:  [Date] [Thread] [Top] [All Lists]