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

Age	Commit message (Collapse)	Author	Files	Lines
2007-10-10	r4063: - change char * -> uint8_t in struct request_buffer	Stefan Metzmacher	1	-3/+3
	- change smbcli_read/write to take void * for the buffers to match read(2)/write(2) all this fixes a lot of gcc-4 warnings metze (This used to be commit b94f92bc6637f748d6f7049f4f9a30b0b8d18a7a)
2007-10-10	r4037: fixed a bunch of "might be uninitialised" warnings after enabling -O1 ↵	Andrew Tridgell	1	-1/+1
	in my compile (This used to be commit 0928b1f5b68c858922c3ea6c27ed03b5091c6221)
2007-10-10	r3574: the RAW-OPEN test changes broke a couple of the other tests. This	Andrew Tridgell	1	-2/+4
	fixes most of them, although RAW-SEARCH still fails (due to an interaction with the new xattr code) (This used to be commit 09b4652b40c4cfca027765178bd5a0adbaa666c2)
2007-10-10	r3447: more include/system/XXX.h include files	Andrew Tridgell	1	-0/+1
	(This used to be commit 264ce9181089922547e8f6f67116f2d7277a5105)
2007-10-10	r3419: moved the libcli/raw structures into libcli/raw/libcliraw.h	Andrew Tridgell	1	-0/+1
	and made them private (This used to be commit 386ac565c452ede1d74e06acb401ca9db99d3ff3)
2007-10-10	r3324: made the smbtorture code completely warning free	Andrew Tridgell	1	-7/+7
	(This used to be commit 7067bb9b52223cafa28470f264f0b60646a07a01)
2007-10-10	r3029: implemented byte range lock timeouts.	Andrew Tridgell	1	-19/+70
	This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557ab175d6a8dd99df03c266325949ffa5)
2007-10-10	r3011: separated the locktest code into a separate module in smbtorture	Andrew Tridgell	1	-0/+907
	(This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)