On 2009-09-15T15:30:14, Florian Haas <[email protected]> wrote:
> No one seems to have acted on this when it was first posted, but we just
> discussed this on #linux-ha, and Lars and Dejan were kind enough to
> offer an explanation:
Why is this cross-posted over 3 lists? One would suffice. Ah well.
> This appears to be the case on any system where libnet (on Debian,
> libnet1-dev) is not available *at compile time*. The obvious workaround,
> per Lars' and Dejan's suggestion, is to compile resource-agents on a
> system with libnet installed.
No, the right solution would be to fix the stand-alone send_arp and drop
the libnet dependency (libnet is not exactly well maintained), and be
rid of the distinction between the two.
The send_arp.linux.c code file has different semantics than
send_arp.libnet.c (I doubt it was ever tested), and can do way more than
we need, but at the same, can't do a few things we want (like sending
both ARP types at once, backgrounding, etc).
A simple 7 step plan if someone feels like coding a bit of C:
1. rm -f send_arp.linux.c
2. mv send_arp.libnet.c send_arp.c
3. vi send_arp.c
4. s/libnet calls/standalone calls/
5. fix build
6. compile
7. ship
Patches welcome ;-)
> Andrew -- assuming you are building packages for RHEL on CentOS, can you
> make sure you pull libnet into the build environment?
RHEL packages get build on RHEL, not on CentOS.
FWIW, this also affects IPaddr.
Regards,
Lars
--
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
