pcp
[Top] [All Lists]

Re: [pcp] PCP Updates: Allow Connection to PMCD via Unix Domain Sockets

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] PCP Updates: Allow Connection to PMCD via Unix Domain Sockets
From: Dave Brolley <brolley@xxxxxxxxxx>
Date: Mon, 15 Jul 2013 15:31:06 -0400
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1032942944.13639792.1373005231784.JavaMail.root@xxxxxxxxxx>
References: <51D5E449.7010304@xxxxxxxxxx> <1032942944.13639792.1373005231784.JavaMail.root@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
On 07/05/2013 02:20 AM, Nathan Scott wrote:
I've also added qa/875 which I think is exposing some issues (no .out file yet as a result) - could you take a look at that for me while I'm away next week? Thanks!!! Test 720 would be a good comparison point. We may have a bit of work to do in __pmUnparseHostAttrsSpec still, and there's lots of nasty looking errors from valgrind coming out the test program (parsehostattrspec.c). cheers. -- Nathan

Hi Nathan,

I've attached two patches for review:
__pmUnparseHostAttrsSpec.patch: Adds the missing code for supporting local:// and unix://. This fixes test 720 and produces reasonable output for test 875 (also attached).

memoryleak.patch: fixes the memory leak in the parsehostattrs.c. I based freeing the hash array in the caller on similar code in logutil.c. Would it may make more sense to free it in __pmFreeHostAttrsSpec()?

Dave

Attachment: __pmUnparseHostAttrsSpec.patch
Description: Text Data

Attachment: memleak.patch
Description: Text Data

Attachment: 875.out
Description: Text document

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