From 4c1c3f2549f32fd069e0e7bf3aec299213f1e85b Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Sun, 25 Oct 2009 16:12:12 +0100 Subject: s3: Implement global locks in a g_lock tdb This is the basis to implement global locks in ctdb without depending on a shared file system. The initial goal is to make ctdb persistent transactions deterministic without too many timeouts. --- source3/librpc/idl/messaging.idl | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'source3/librpc/idl') diff --git a/source3/librpc/idl/messaging.idl b/source3/librpc/idl/messaging.idl index 068658587f..08caa59508 100644 --- a/source3/librpc/idl/messaging.idl +++ b/source3/librpc/idl/messaging.idl @@ -88,7 +88,8 @@ interface messaging MSG_DUMP_EVENT_LIST = 0x0500, /* dbwrap messages 4001-4999 */ - MSG_DBWRAP_TDB2_CHANGES = 4001 + MSG_DBWRAP_TDB2_CHANGES = 4001, + MSG_DBWRAP_G_LOCK_RETRY = 4002 } messaging_type; /* messaging struct sent across the sockets and stored in the tdb */ -- cgit