mingdao lu wrote:
> I have very special application case based on Heartbeat 2 framwork. In
> the application, it grasp all packages received on the ethernet port,
> including the heartbeat UDP and ARP broadcast packages. So the Heartbeat
> functions can not receive any packages from kernel automatically.
> I have 2 questions about this senario.
> 
> 1, Besides UDP and ARP broadcast, what else TCP/IP protocols are used in
> Heartbeat 2 function.
> 
> 2, Where is the entrance for heartbeat to handle UDP and ARP broadcast
> packages? I intend to send these grasped UDP and ARP packages to
> Heartbeat process manually. So I need to know how heartbeat handles
> these packages.

When you say "packages" I assume you mean "packets".

Heartbeat does communication within a machine by local domain (UNIX
domain) sockets for IPC.

Communication between machines is done by plugin.  If you wrote another
communications plugin, you could talk by something that didn't involve
sockets.

Those are found in the lib/plugins/HBcomm directory.

The management daemon also talks across sockets, but that's an optional
component - which if you don't want the GUI, isn't necessary.


-- 
    Alan Robertson <[EMAIL PROTECTED]>

"Openness is the foundation and preservative of friendship...  Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Reply via email to