summaryrefslogtreecommitdiff
path: root/source3/utils/locktest.c
AgeCommit message (Collapse)AuthorFilesLines
2000-05-06signed/unsigned fixes so we can handle a lock base close to 2^32Andrew Tridgell1-31/+29
(This used to be commit 0ce2ca5ccdd0e2e7711dcbf66b72a183b2692cfe)
2000-05-05make debug easier to readAndrew Tridgell1-6/+9
(This used to be commit c14a2616441b2f3357a081c6dbae7d5b677e5a12)
2000-05-05make debug easier to readAndrew Tridgell1-5/+6
(This used to be commit d64bb07f0ad0efa1a20015b620ae33fb082b1e44)
2000-05-05nasty hack to print posix locksAndrew Tridgell1-0/+17
(This used to be commit efc9752f1e00b38abe3b5d3a98627a9fe6122bc4)
2000-05-05example of broken posix lock behaviourAndrew Tridgell1-0/+8
(This used to be commit b3999f3b20d470b9c873b297e7aeb043da61588d)
2000-05-04parameterize the lock timeoutAndrew Tridgell1-2/+3
(This used to be commit 98ad4095ccc8d0349d05e6e9223eaad057029626)
2000-05-04an even simpler example of NT gettings its locking code wrong. ThisAndrew Tridgell1-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. (This used to be commit 0b335e415818028ac0daad5f99c2fd9086a2a656)
2000-05-04need LOCKING_OBJ in locktest nowAndrew Tridgell1-3/+7
(This used to be commit 89e71994450f479a0f3839f192d868924626fc84)
2000-05-04more locktest improvementsAndrew Tridgell1-31/+81
the current preset tests show a very interesting NT bug - it sometimes refuses a lock that it shouldn't. (This used to be commit 85b5dc64cf7cc80567f9069a48c4d20c10ccec01)
2000-05-04added -A analyze mode to locktest - it can now automatically pruneAndrew Tridgell1-139/+242
the list of locks that cause a failure (This used to be commit 0beee59432f17f90a1c4c2c68a7ea6022b5d0908)
2000-05-04found a much simpler case that kills the posix lockingAndrew Tridgell1-5/+5
(This used to be commit b703cecf81dc62234171eaaa4c0cae448f144e1f)
2000-05-04fixed a uninit memory read that insure foundAndrew Tridgell1-6/+3
(This used to be commit 43fe5b98b4514d59e1c4bbc54a628cfbd771fc4f)
2000-05-04added ability to present lock testsAndrew Tridgell1-16/+40
(This used to be commit 3fc6a467fc3dfd2a59d4509ec52172d2dd048c80)
2000-05-03improved the lock test programAndrew Tridgell1-15/+27
(This used to be commit a0a3931c6e5824121bf4a8d075ef24b9b70e8aa1)
2000-05-03added a nasty lock testing programAndrew Tridgell1-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. (This used to be commit 2f14d7c9bca5e170b8d2c169801cb200021fd467)