Hi,
I have been looking into the the last two (known) TODOs for IPv6 on
my list:
libpcp_pmda:
pmdaConnect() in open.c calls __pmdaOpenInet() or
__pmdaOpenUnix() depending on the value of the e_io field of the
supplied pmdaInterface. The approach we have been taking to pcp
daemons, in keeping with ipv6+inet as a transitional situation, is
that they should listen on both inet and ipv6 simultaneously. It
would be easy to add support to the pmdaInterface type for more
than one open 'in_fd', similar to what has been added in
src/libpcp/src/secureserver.c. When pmdaInet is configured with
e_io==pmdaInet, then both an inet and ipv6 socket would be opened.
Technically, this seems reasonable to me. My main concern would be
that pmdaInet and __pmdaOpenInet() would become somewhat misnamed.
Options are to a) not worry about it, b) rename these items c) add
the new behaviour and appropriately named API extensions to pmda
interface version 6, leaving the previous versions alone.
Some guidance here would be appreciated.
src/pmdas/trace:
This component appears to have a listening socket for
control purposes, in addition to the one obtained for libpcp_pmda
for communicating with the pmcd. It seems reasonable the IPv6
connections should also be accepted here. Any thoughts?
Thanks,
Dave
|
|