summaryrefslogtreecommitdiff
path: root/source4/include/messages.h
AgeCommit message (Collapse)AuthorFilesLines
2007-10-10r3029: implemented byte range lock timeouts.Andrew Tridgell1-45/+1
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)
2003-08-13first public release of samba4 codeAndrew Tridgell1-0/+75
(This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)