Ronnie Sahlberg 69f3a09e6f when a remote node has sent us a message to update the flags for a node, ...

dont let those messages modify the DISCONNECTED flag.

the DISCONNECTED flag must be managed locally since it describes whether 
the local node can communicate with the remote node or not

(This used to be ctdb commit 5650673205d335a32d4f27f66847ea66752a00f0)

2007-07-09 13:21:17 +10:00

..

ctdb_call.c

log the generation numbers to give a hint about this bug

2007-07-08 19:36:55 +10:00

ctdb_control.c

propogate flag changes to all connected nodes

2007-06-09 21:58:50 +10:00

ctdb_daemon.c

added code to kill registered clients on a IP release

2007-06-19 03:54:06 +10:00

ctdb_freeze.c

- send tcp info to all connected nodes, not just vnnmap nodes

2007-06-10 08:46:33 +10:00

ctdb_lockwait.c

start splitting the code into separate client and server pieces

2007-06-07 22:06:19 +10:00

ctdb_ltdb_server.c

- merged ctdb_store test from ronnie

2007-06-17 23:31:44 +10:00

ctdb_monitor.c

- send tcp info to all connected nodes, not just vnnmap nodes

2007-06-10 08:46:33 +10:00

ctdb_recover.c

- merged ctdb_store test from ronnie

2007-06-17 23:31:44 +10:00

ctdb_recoverd.c

when a remote node has sent us a message to update the flags for a node,

2007-07-09 13:21:17 +10:00

ctdb_server.c

added code to kill registered clients on a IP release

2007-06-19 03:54:06 +10:00

ctdb_takeover.c

fixed sense of inet_aton test

2007-07-08 21:09:09 +10:00

ctdb_traverse.c

added code to kill registered clients on a IP release

2007-06-19 03:54:06 +10:00

ctdb_tunables.c

add a tuneable to control how long we wait after a successful recovery

2007-07-04 08:36:59 +10:00

ctdbd.c

start splitting the code into separate client and server pieces

2007-06-07 22:06:19 +10:00

eventscript.c

forgot to add this

2007-07-04 17:45:46 +10:00