pcp
[Top] [All Lists]

Re: [pcp] QA status - warning

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] QA status - warning
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 7 May 2013 19:53:11 -0400 (EDT)
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <51889F39.8060206@xxxxxxxxxxxxxxxx>
References: <51823EB3.1030003@xxxxxxxxxxxxxxxx> <410335498.9468044.1367544497012.JavaMail.root@xxxxxxxxxx> <851894341.11621320.1367881806756.JavaMail.root@xxxxxxxxxx> <2055430036.11651048.1367887214801.JavaMail.root@xxxxxxxxxx> <51889F39.8060206@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: ug0nfaH1VIiNVq1NGRtoplHHKTO0kA==
Thread-topic: QA status - warning
Hi Ken,

----- Original Message -----
> On 07/05/13 10:40, Nathan Scott wrote:
> > ...
> > There's still something wrong here - MMV state is getting changed
> > during the QA run ... this looks like it may be fallout from the
> > series of QA changes around the time of:
> 
> Yep, my fault I'm afraid ... sorry about that.
> 
> Attempting to put pmda installation back the way it was, but for the mmv
> pmda ./Install </dev/null forces the mmv pmda to be installed as a daemon.
> 
> Fix/commit on its way as soon as I've tested it.
> 

No problem.  I wonder if the pmdammv Install script should strive for a
DSO installation by default, since thats what the build/packaging does?
(not sure if that is possible with pmdaproc.sh though)

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>