On Wed, 27 Aug 2014, Matt W. Benjamin wrote: > > ----- "Sage Weil" <sweil at redhat.com> wrote: > > > > What would be best way for us to mark which sockets are heartbeat > > related? > > Is there some setsockopt() type call we should be using, or should we > > > > perhaps use a different port range for heartbeat traffic? > > Would be be plausible to have hb messengers identify themselves to a bus as such, > that external tools (here, the ts scripts) could introspect? What do you mean by bus in this case? I seem to remember someone telling me there were hooks/hints you could call that would tag either a socket or possibly data on that socket with a label for use by iptables and such.. but I forget what it was. sage