On 05/13/2013 11:52 PM, Nathan Scott wrote:
The PMDA/PMCD relationship is quite a bit different to the client/pmcd
relationship - its one-to-one (noone else will be communicating on this
channel) and is much more controlled. So, I don't think opening ports
for both ipv6 and inet is warranted in the PMDA case, and this should
simplify things. Back-compatibility is required, and this ipv6 option
should be available transparently to all PMDAs that support sockets.
As posted to the project list, I've added a -6 option to pmdaGetOpt()
for requesting an IPv6 socket. Should I go ahead and a "6:" to the
option strings of all the callers as well?
So, the pmcd.conf parsing should be extended to have an "ipv6" style of
socket (alongside unix and inet - start from pmcd/src/config.c line 680
or so), and this should be propagated around including the spots you've
listed above. Ultimately, it should be an ./Install-time decision for
an admin to make, should they choose to go with the socket connection
option for any given PMDA.
I
I'll look at this next.
Dave
|