Rusty Russell 928b8dcb31 eventscript: handle banning within the callbacks ...

Currently the timeout handler in eventscript.c does the banning if a
timeout happens.  However, because monitor events are different, it has
to special case them.

As we call the callback anyway in this case, we should make that handle
-ETIME as it sees fit: for everyone but the monitor event, we simply ban
ourselves.  The more complicated monitor event banning logic is now in
ctdb_monitor.c where it belongs.

Note: I wrapped the other bans in "if (status == -ETIME)", though they
should probably ban themselves on any error.  This change should be a
noop.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>


(This used to be ctdb commit 9ecee127e19a9e7cae114a66f3514ee7a75276c5)

2009-12-07 23:48:57 +10:30

..

ctdb_banning.c

eventscript: expost ctdb_ban_self()

2009-12-07 23:18:40 +10:30

ctdb_call.c

Revert "From Wolfgang M."

2009-10-29 13:44:12 +11:00

ctdb_control.c

eventscript: use -ENOEXEC for disabled status value

2009-12-07 23:11:47 +10:30

ctdb_daemon.c

lower the loglevel for the message that a client has attached through a domian socket

2009-12-02 14:51:57 +11:00

ctdb_freeze.c

change the lock wait child handling to use a pipe isntead of a socketpair

2009-11-26 12:08:35 +11:00

ctdb_keepalive.c

add a new node state : DELETED.

2009-06-01 14:18:34 +10:00

ctdb_lockwait.c

add logging everytime we create a filedescriptor in the main ctdb daemon

2009-10-15 11:24:54 +11:00

ctdb_logging.c

add an in memory ringbuffer where we store the last 500000 log entries regardless of log level.

2009-11-18 12:44:18 +11:00

ctdb_ltdb_server.c

lower the loglevel for the message that a client has attached to a persistent database

2009-12-02 14:53:21 +11:00

ctdb_monitor.c

eventscript: handle banning within the callbacks

2009-12-07 23:48:57 +10:30

ctdb_persistent.c

server:trans2_commit: move the check for active recovery down.

2009-12-04 15:03:21 +01:00

ctdb_recover.c

eventscript: handle banning within the callbacks

2009-12-07 23:48:57 +10:30

ctdb_recoverd.c

recovery: add special pull-logic for persistent databases

2009-12-04 15:00:21 +01:00

ctdb_server.c

make it possible to start the daemon in STOPPED mode

2009-07-09 11:57:20 +10:00

ctdb_serverids.c

merge from ronnie

2008-02-04 20:07:15 +11:00

ctdb_takeover.c

eventscript: handle banning within the callbacks

2009-12-07 23:48:57 +10:30

ctdb_traverse.c

add logging everytime we create a filedescriptor in the main ctdb daemon

2009-10-15 11:24:54 +11:00

ctdb_tunables.c

test of a change to make ctdbd use "status" event instead of the "monitor" event.

2009-11-13 12:37:55 +11:00

ctdb_uptime.c

track both when we last started and ended a recovery.

2008-07-02 13:55:59 +10:00

ctdb_vacuum.c

reduce the log level for three vacuuming related log messages

2009-11-24 09:27:22 +11:00

ctdbd.c

start the syslog child a little later, after we have forked and detached from the local shell

2009-10-30 19:39:11 +11:00

eventscript.c

eventscript: handle banning within the callbacks

2009-12-07 23:48:57 +10:30