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

Age	Commit message (Collapse)	Author	Files	Lines
2011-03-30	s3-includes: only include system/filesys.h when needed.	Günther Deschner	1	-0/+1
	Guenther
2011-02-17	s3-cluster Always fill in the clustering vnn element	Andrew Bartlett	1	-6/+0
	This avoids this structure being partially uninitialised. Adnrew Bartlett
2010-12-19	s3: Fix serverid_exists	Volker Lendecke	1	-0/+4
	In the cluster case it can happen that a node just died and we did not yet have the time to clean up serverid.tdb. If the corresponding serverid.tdb record that represented a process was migrated away from the dead record, it represents existence of a process where it is already dead.
2010-09-27	Change to using TDB_INCOMPATIBLE_HASH (the jenkins hash) on all	Jeremy Allison	1	-2/+2
	TDB_CLEAR_IF_FIRST tdb's. For tdb's like gencache where we open without CLEAR_IF_FIRST and then with CLEAR_IF_FIRST if corrupt this is still safe to use as if opening an existing tdb the new hash will be ignored - it's only used on creating a new tdb not opening an old one. Jeremy.
2010-09-26	s3: Remove talloc_autofree_context() from serverid_db()	Volker Lendecke	1	-2/+2
	If we needed an explicit tdb_close() in the destructor, we'd be hosed long ago.
2010-09-26	s3: Remove talloc_autofree_context() from serverid_parent_init()	Volker Lendecke	1	-3/+2

2010-08-26	s3-build: use dbwrap.h only where needed.	Günther Deschner	1	-0/+1
	Guenther
2010-08-18	s3: Fix serverid_register_msg_flags	Volker Lendecke	1	-4/+2
	Thanks, Andreas, for pointing this out! (How drunk have I been?...)
2010-08-18	s3-lib: Fixed a possible crash bug.	Andreas Schneider	1	-0/+2
	Volker please check!
2010-07-20	Fix warning on 64-bit machines.	Jeremy Allison	1	-1/+1
	Jeremy.
2010-07-05	s3: Put serverid_key and serverid_data together	Volker Lendecke	1	-5/+5

2010-07-04	s3: Remove an unused variable -- thanks, metze!	Volker Lendecke	1	-2/+1

2010-07-04	s3: Replace register_message_flags() with serverid_register_msg_flags()	Volker Lendecke	1	-0/+52
	message_send_all is now done by walking the serverid.tdb, not the connections.tdb anymore. Günther, Simo, please check!
2010-07-04	s3: Remove serverid_[de]register_self	Volker Lendecke	1	-21/+5
	This removes some deep references to procid_self()
2010-07-04	s3: ALWAYS run make test before checkin ....	Volker Lendecke	1	-2/+2

2010-07-04	s3: Slight reshaping of server_exists_parse	Volker Lendecke	1	-4/+6
	Doing a copy and then do the compare is a bit pointless, use memcmp
2010-03-25	s3: Add a comment to serverid_parent_init, this is pretty confusing	Volker Lendecke	1	-0/+6

2010-03-25	s3: Make sure our CLEAR_IF_FIRST optimization works for serverid.tdb	Volker Lendecke	1	-0/+16
	In the child, we fully re-open serverid.tdb, which leads to one fcntl lock for CLEAR_IF_FIRST detection per smbd. This opens the tdb in the parent and holds it, so that tdb_reopen_all correctly catches the CLEAR_IF_FIRST bit.
2010-03-10	s3: Fix a long-standing problem with recycled PIDs	Volker Lendecke	1	-0/+293
	When a samba server process dies hard, it has no chance to clean up its entries in locking.tdb, brlock.tdb, connections.tdb and sessionid.tdb. For locking.tdb and brlock.tdb Samba is robust by checking every time we read an entry from the database if the corresponding process still exists. If it does not exist anymore, the entry is deleted. This is not 100% failsafe though: On systems with a limited PID space there is a non-zero chance that between the smbd's death and the fresh access, the PID is recycled by another long-running process. This renders all files that had been locked by the killed smbd potentially unusable until the new process also dies. This patch is supposed to fix the problem the following way: Every process ID in every database is augmented by a random 64-bit number that is stored in a serverid.tdb. Whenever we need to check if a process still exists we know its PID and the 64-bit number. We look up the PID in serverid.tdb and compare the 64-bit number. If it's the same, the process still is a valid smbd holding the lock. If it is different, a new smbd has taken over. I believe this is safe against an smbd that has died hard and the PID has been taken over by a non-samba process. This process would not have registered itself with a fresh 64-bit number in serverid.tdb, so the old one still exists in serverid.tdb. We protect against this case by the parent smbd taking care of deregistering PIDs from serverid.tdb and the fact that serverid.tdb is CLEAR_IF_FIRST. CLEAR_IF_FIRST does not work in a cluster, so the automatic cleanup does not work when all smbds are restarted. For this, "net serverid wipe" has to be run before smbd starts up. As a convenience, "net serverid wipedbs" also cleans up sessionid.tdb and connections.tdb. While there, this also cleans up overloading connections.tdb with all the process entries just for messaging_send_all(). Volker