Preston Smith wrote:
On Mon, Sep 16, 2002 at 06:08:21PM -0700, Federico Sacerdoti ([EMAIL
PROTECTED]) wrote:
Q. Why do we use libdnet?
A. Many things in unix are fairly similar across various OS flavors, whereas something as simple
as wanting to know "what are all the network interfaces on this box?" or "which
network interfaces are multicast-enabled?" is not easy. Libdnet provides a uniform API to help
answer these network-related questions. We currently use libdnet to query multicast-enabled network
interfaces on a machine, and for metrics such as MTU. However, our tests show the version of
libdnet we use does not support AIX fully.
What doesn't work on AIX? I've fixed any dnet problems I've encountered,
(particularly with the stupid thing not building). My impression from
dnet's own faq is that arp and route stuff is all that doesn't fully support
AIX, and ganglia doesn't even use them..
I've not had any problems with any of the dnet stuff on AIX, but I'm not
doing anything fancy with multicast routes, different channels, or multiple
interfaces on AIX.. There's the grain of salt.
Just curious, and if there's a problem, I'll try and help find a
fix/workaround for 2.5.0.
I've experienced some problems with it on IRIX and Solaris 8, as mentioned
earlier. IRIX support seems to be shakier - Solaris at least auto-detects
interfaces correctly. But both will segfault on the real mtu_func code...
