effect but allows the processor to participate in multicasting
and membership.
(Logical change 1.38)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@112 fd59a12c-fef9-0310-b244-a6a79926bd2f
that occurred during configuration changes. The result was bad
behavior, especially with larger rings. Also cleaned up the
token retransmit timer to be deleted if necessary.
(Logical change 1.37)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@110 fd59a12c-fef9-0310-b244-a6a79926bd2f
2004/07/12 14:37:13-07:00 mvista.com!sdake
When a processor left the membership, the next configuration would sometimes
cause a form token timeout. While not particularly harmful, it was wasteful
and not part of the original design of the group messaging protocol.
There was some extra junk code that was added to workaround some other bug
that has since been fixed.
This junk code removed and now the form token never times out (woohoo).
Also removed some extra code that calculates the next ORF processor twice.
We only really need to do it once.
(Logical change 1.33)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@100 fd59a12c-fef9-0310-b244-a6a79926bd2f
within a timeout period (100 msec). This helps avoid
a reconfiguration when only the token is lost, but no
real configuration changes have occured.
(Logical change 1.32)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@98 fd59a12c-fef9-0310-b244-a6a79926bd2f
the conn_info structure.
the track list was not being initialized at start.
(Logical change 1.27)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@82 fd59a12c-fef9-0310-b244-a6a79926bd2f
conn_info structure.
the track list was not being initialized. When track start was called
the tracking wasn't added to a list. When track stop was called
the tracking was not deleted.
The result of all this is that cluster membership tracking was broken
previously.
(Logical change 1.27)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@80 fd59a12c-fef9-0310-b244-a6a79926bd2f
This requires changing the initialization phase of the socket
and all calls made.
(Logical change 1.24)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@75 fd59a12c-fef9-0310-b244-a6a79926bd2f
this requires removing the connection structure and replacing
with the conn_info structure.
(Logical change 1.24)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@70 fd59a12c-fef9-0310-b244-a6a79926bd2f
a memcpy with a -1 value in some cases, and the incorrect memcpy
in other cases.
(Logical change 1.20)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@49 fd59a12c-fef9-0310-b244-a6a79926bd2f
didn't sent the appropriate configuration changes to the clm API
or to the rest of the services.
(Logical change 1.19)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@48 fd59a12c-fef9-0310-b244-a6a79926bd2f
it is possible to specify the bind network and
the networking will take place over that interface.
(Logical change 1.14)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@30 fd59a12c-fef9-0310-b244-a6a79926bd2f
as root in order to lock, set RR 99, and
bind to a specific ethernet interface for multicast.
(Logical change 1.14)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@29 fd59a12c-fef9-0310-b244-a6a79926bd2f
UDP sockets, bind to specific interface defined in network.conf.
This is done by creating two fds. gmi_fd_token is used for all
token communication. gmi_fd_mcast is used for all mcast
communication. I'm not sure if gmi_fd_mcast binding rules is
correct. Once work begins on multipathing, this will have to
be figured out :)
2004/06/23 13:55:52-07:00 mvista.com!sdake
Use portable mreq instead of mreqn when joining the multicast
group.
(Logical change 1.13)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@26 fd59a12c-fef9-0310-b244-a6a79926bd2f
port being byte swapped. This of course, doesn't work well with
xscale boards.
(Logical change 1.9)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@17 fd59a12c-fef9-0310-b244-a6a79926bd2f
the recursion by queueing single node message delivery as a timer
with 0 timeout. This was happening before, but the logic was
wrong.
(Logical change 1.7)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@13 fd59a12c-fef9-0310-b244-a6a79926bd2f
