pcp
[Top] [All Lists]

Re: [pcp] PCP Updates -- Remove inet-specific API Use in Favour of the l

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] PCP Updates -- Remove inet-specific API Use in Favour of the libpcp I/O API
From: Dave Brolley <brolley@xxxxxxxxxx>
Date: Thu, 24 Apr 2014 17:36:16 -0400
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1204878828.10178271.1398311378294.JavaMail.zimbra@xxxxxxxxxx>
References: <360594769.5718335.1381470346334.JavaMail.root@xxxxxxxxxx> <5357FA37.2070202@xxxxxxxxxx> <1204878828.10178271.1398311378294.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
On 04/23/2014 11:49 PM, Nathan Scott wrote:

----- Original Message -----
These commits, on the brolley/dev branch of pcpfans remove the use of
inet-specific APIs (i.e. no ipv6) in favour of the libpcp I/O APIs (which do
support IPv6, where available).

The original message from Nathan which inspired this can be found below.

Some __pm level functions which were previously static were moved to impl.h
in order to accomplish this.

A local qa run shows no regressions.
Looking good Dave.  I hit one regression over in test 589 - looks like
telnet-probe is not quite right.  Diff below, I've push the merge into
my own dev branch on oss; its the same as yours with a pmdacisco merge
conflict sorted out.  The failure looks like a non-blocking I/O issue
of some kind during connect(2).

I've investigated and fixed this problem. Currently doing a new qa run.

Dave

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