RE: [pcp] pcp QA status

["Ken McDonell" <kenj@xxxxxxxxxxxxxxxx>]

> -----Original Message-----
> From: Nathan Scott [mailto:nathans@xxxxxxxxxx]
> Sent: Friday, 24 June 2016 12:09 PM
> ...
> Ken, is it always non-secure-sockets builds that fail with your QA
> hosts?
> (pmconfig  -L secure_sockets)

For me 651 is failing on

vm01 PCP 3.11.4   i686    Ubuntu 15.10 (wily)
        secure_sockets=true

vm23 PCP 3.11.4   i686    Fedora 20 (Heisenbug)
        secure_sockets=true

vm25 PCP 3.11.3   x86_64  CentOS 5.11 (Final)
        secure_sockets=true

vm28 PCP 3.11.4   x86_64  RHEL Server 6.8 (Santiago)
        secure_sockets=true

So secure sockets or not are out of the frame it would appear.

qa/651 discards pmproxy.log ... fixed that

pmproxy does not open log file early enough so running pmproxy -Dcontext leaks 
diags into .out file ... fixed that

qa/651 had wrong (looking) logic testing id pcp, then running pmproxy with -U 
myusername ... changed to -U pcp

And it passes everywhere for me.

I'll leave it to someone who knows to explain this.

All these changes are my latest round of commits.