summaryrefslogtreecommitdiffstats
path: root/source/utils/locktest.c
Commit message (Collapse)AuthorAgeFilesLines
* Start of merge to 2_2_RELEASE branch for release.Jeremy Allison2002-04-301-7/+11
| | | | Jeremy.
* Move over to RELEASE branch.Jeremy Allison2002-02-011-1/+1
| | | | Jeremy.
* Adnrew's 64 bit locking fixes for RedHat 7.0.... (sigh). They don'tJeremy Allison2000-09-291-19/+19
| | | | | seem to peturb much. Jeremy.
* slightly saner defaultsAndrew Tridgell2000-06-291-3/+3
|
* allow for lots of connections per serverAndrew Tridgell2000-06-131-75/+76
|
* don't ue nasty /proc/locks hack by defaultAndrew Tridgell2000-06-051-2/+2
|
* added -O (use oplocks) option to locktestAndrew Tridgell2000-06-051-1/+8
|
* minor fixesAndrew Tridgell2000-05-241-4/+0
|
* added -u hide_unlock_fails optionAndrew Tridgell2000-05-241-2/+7
|
* use lp_workgroup()Andrew Tridgell2000-05-241-3/+4
| | | | use \\ in front of filenames
* Added -W workgroup command line option.Tim Potter2000-05-221-1/+6
| | | | Added call to codepage_initialise().
* signed/unsigned fixes so we can handle a lock base close to 2^32Andrew Tridgell2000-05-061-31/+29
|
* make debug easier to readAndrew Tridgell2000-05-051-6/+9
|
* make debug easier to readAndrew Tridgell2000-05-051-5/+6
|
* nasty hack to print posix locksAndrew Tridgell2000-05-051-0/+17
|
* example of broken posix lock behaviourAndrew Tridgell2000-05-051-0/+8
|
* parameterize the lock timeoutAndrew Tridgell2000-05-041-2/+3
|
* an even simpler example of NT gettings its locking code wrong. ThisAndrew Tridgell2000-05-041-20/+14
| | | | | | | | one doesn't even need two connections to the box, just two file handles. it is a very simple case actually, and one I think will happen quite a lot in real life. I wonder how they haven't noticed it? I checked and W2K has the same bug.
* need LOCKING_OBJ in locktest nowAndrew Tridgell2000-05-041-3/+7
|
* more locktest improvementsAndrew Tridgell2000-05-041-31/+81
| | | | | the current preset tests show a very interesting NT bug - it sometimes refuses a lock that it shouldn't.
* added -A analyze mode to locktest - it can now automatically pruneAndrew Tridgell2000-05-041-139/+242
| | | | the list of locks that cause a failure
* found a much simpler case that kills the posix lockingAndrew Tridgell2000-05-041-5/+5
|
* fixed a uninit memory read that insure foundAndrew Tridgell2000-05-041-6/+3
|
* added ability to present lock testsAndrew Tridgell2000-05-041-16/+40
|
* improved the lock test programAndrew Tridgell2000-05-031-15/+27
|
* added a nasty lock testing programAndrew Tridgell2000-05-031-0/+340
it opens 2 connections to each of 2 servers, and opens 2 fnums on the same file on each connection (a total of 8 file descriptors) then it does random lock/unlock/reopen requests in a 100 byte range on the file and compares the results from the 2 servers. strangely enough, NT fails this test against itself right now - I'm still trying to figure that out.