samba - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2012-06-19	Fix warning: variable ‘status’ set but not used.	Jeremy Allison	1	-2/+1

2012-04-19	s3-g_lock: Use dbwrap_record_watch_send/recv	Volker Lendecke	1	-3/+2
	This simplifies the g_lock implementation. The new implementation tries to acquire a lock. If that fails due to a lock conflict, wait for the g_lock record to change. Upon change, just try again. The old logic had to cope with pending records and an ugly hack into ctdb itself. As a bonus, we now get a really clean async g_lock_lock_send/recv that can asynchronously wait for a global lock. This would have been almost impossible to do without the dbwrap_record_watch infrastructure.
2011-12-12	s3: Remove a bunch of calls to procid_self()	Volker Lendecke	1	-2/+2
	All callers to messaging_[re]init only used procid_self()
2011-06-20	tdb_traverse/tdb_traverse_read: check returns for negative, not -1.	Rusty Russell	1	-1/+1
	TDB2 returns a negative error number on failure. This is compatible if we always check for < 0 instead of == -1. Also, there's no tdb_traverse_read in TDB2: we don't try to make traverse reliable any more, so there are no write locks anyway. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2011-06-09	lib/util Bring procid_str() into lib/util as server_id_string()	Andrew Bartlett	1	-1/+1
	This is needed for OpenChange, which prints Samba struct server_id values in debug messages. Andrew Bartlett
2011-03-30	s3-messages: only include messages.h where needed.	Günther Deschner	1	-0/+1
	Guenther
2010-08-28	s3: Remove the dependency of g_lock on procid_self	Volker Lendecke	1	-1/+1
	procid_self() references global vars, don't depend on them unnecessarily
2010-03-12	s3: Add "g_lock_do" as a convenience wrapper function	Volker Lendecke	1	-27/+22

2010-03-12	s3: Actually use mem_ctx in net_g_lock_init()	Volker Lendecke	1	-3/+3

2010-02-23	s3: Consolidate server_id_self into the equivalent procid_self()	Volker Lendecke	1	-1/+1

2010-02-12	s3: Implement global locks in a g_lock tdb	Volker Lendecke	1	-0/+213
	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.