On 2006-06-28T17:32:32, David Lee <[EMAIL PROTECTED]> wrote:
> I was wondering whether the protocol is described somewhere (in similar
> manner to RFCs describing SMTP, TCP, etc.). Alternatively, whether the
> expected (designed) internal operation of lrmd was documented.
Well, the protocol is not meant to be re-implemented anywhere, so the
documentation seems to be in the code itself.
A slightly more formal description would be cool, but I don't think that
rates very high on our list.
> The hanging "lrmadmin" was from "STONITHDBasicSanityCheck" where it does
> the "lrmadmin -E s1 start 0 0 0".
>
> Note that on a different subthread of this topic, Alan has suggested that
> I open a bugzilla report. (And Matt Soffen, another heartbeat developer
> using non-Linux, has also just reported a problem.)
>
> So a little documentation about how it is _designed_ to work would help
> folk like Matt and me chase problems.
This looks more as if lrmd/lrmadmin can't even properly communicate.
My uneducated guess would be that you don't need the lrmd documented,
but the IPC layer we use, and then make sure that the streams
implementation behaves exactly the same. Perhaps even sockets (when not
using streams) behave differently on different flavors of Unix, in
particular wrt non-blocking use.
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
