14 Commits

Author	SHA1	Message	Date
Jelmer Vernooij	c722f665c9	r12694: Move some headers to the directory of the subsystem they belong to.	2007-10-10 13:49:39 -05:00
Jelmer Vernooij	73610639b2	r12693: Move core data structures out of smb.h into core.h ... torture prototypes in seperate header	2007-10-10 13:49:39 -05:00
Andrew Tridgell	a58ea6b385	r8520: fixed a pile of warnings from the build farm gcc -Wall output on ... S390. This is an attempt to avoid the panic we're seeing in the automatic builds. The main fixes are: - assumptions that sizeof(size_t) == sizeof(int), mostly in printf formats - use of NULL format statements to perform dn searches. - assumption that sizeof() returns an int	2007-10-10 13:29:34 -05:00
Andrew Tridgell	0b22744f40	r8117: fixed a bunch more dos error code handing. ... The biggest change was fixing the RAW-CONTEXT test. It was forcing capabilities to zero in an attempt to not negotiated extended security, but as a side effect it was forcing negotiation of dos error codes. This confused the hell out of the test code! Also fixed a bunch of places incorrectly using NT_STATUS_V() instead of NT_STATUS_EQUAL() and several places that had the wrong dos status codes	2007-10-10 13:19:10 -05:00
Andrew Tridgell	9db6c79e90	r5298: - got rid of pstring.h from includes.h. This at least makes it a bit ... less likely that anyone will use pstring for new code - got rid of winbind_client.h from includes.h. This one triggered a huge change, as winbind_client.h was including system/filesys.h and defining the old uint32 and uint16 types, as well as its own pstring and fstring.	2007-10-10 13:09:38 -05:00
Andrew Tridgell	a44fa5319d	r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, ... thus avoiding errors due to previous failures	2007-10-10 13:07:48 -05:00
Stefan Metzmacher	b94f92bc66	r4063: - change char * -> uint8_t in struct request_buffer ... - 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	2007-10-10 13:06:21 -05:00
Andrew Tridgell	0928b1f5b6	r4037: fixed a bunch of "might be uninitialised" warnings after enabling -O1 in my compile	2007-10-10 13:06:16 -05:00
Andrew Tridgell	09b4652b40	r3574: the RAW-OPEN test changes broke a couple of the other tests. This ... fixes most of them, although RAW-SEARCH still fails (due to an interaction with the new xattr code)	2007-10-10 13:05:33 -05:00
Andrew Tridgell	264ce91810	r3447: more include/system/XXX.h include files	2007-10-10 13:05:12 -05:00
Andrew Tridgell	386ac565c4	r3419: moved the libcli/raw structures into libcli/raw/libcliraw.h ... and made them private	2007-10-10 13:05:07 -05:00
Andrew Tridgell	7067bb9b52	r3324: made the smbtorture code completely warning free	2007-10-10 13:04:55 -05:00
Andrew Tridgell	4395c0557a	r3029: implemented byte range lock timeouts. ... 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.	2007-10-10 13:00:00 -05:00
Andrew Tridgell	f4a91be635	r3011: separated the locktest code into a separate module in smbtorture	2007-10-10 12:59:57 -05:00