From 1ebfc66b2c145289d1e1314e8415d9e3c6f405ae Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Mon, 10 Mar 2008 21:08:29 +0100 Subject: Use a separate tdb for mutexes Another preparation to convert secrets.c to dbwrap: The dbwrap API does not provide a sane tdb_lock_with_timeout abstraction. In the clustered case the DC mutex is needed per-node anyway, so it is perfectly fine to use a local mutex only. (This used to be commit f94a63cd8f94490780ad9331da229c0bcb2ca5d6) --- source3/include/smb.h | 1 + 1 file changed, 1 insertion(+) (limited to 'source3/include/smb.h') diff --git a/source3/include/smb.h b/source3/include/smb.h index c582a97e5c..bf9ca6b92c 100644 --- a/source3/include/smb.h +++ b/source3/include/smb.h @@ -420,6 +420,7 @@ struct timed_event; struct idle_event; struct share_mode_entry; struct uuid; +struct named_mutex; struct vfs_fsp_data { struct vfs_fsp_data *next; -- cgit