summaryrefslogtreecommitdiff
path: root/source3/torture/test_cleanup.c
AgeCommit message (Collapse)AuthorFilesLines
2013-09-03torture3: Trigger a nasty cleanup bug in smbdVolker Lendecke1-0/+70
Signed-off-by: Volker Lendecke <vl@samba.org> Reviewed-by: Michael Adam <obnox@samba.org> Autobuild-User(master): Michael Adam <obnox@samba.org> Autobuild-Date(master): Tue Sep 3 19:13:14 CEST 2013 on sn-devel-104
2012-05-25s3: Test whether get_share_mode_lock cleans up stale processesVolker Lendecke1-0/+175
Signed-off-by: Jeremy Allison <jra@samba.org> Signed-off-by: Stefan Metzmacher <metze@samba.org>
2012-05-18s3: Revert the serverid changes, they need more workVolker Lendecke1-175/+0
Autobuild-User: Volker Lendecke <vl@samba.org> Autobuild-Date: Fri May 18 13:12:14 CEST 2012 on sn-devel-104
2012-05-17s3: Test whether get_share_mode_lock cleans up stale processesVolker Lendecke1-0/+175
Signed-off-by: Jeremy Allison <jra@samba.org>
2012-01-06s3: Use DELETE_ON_CLOSE instead of unlinkVolker Lendecke1-7/+6
2012-01-05s3: Add a test for proper brlock cleanupVolker Lendecke1-0/+87
We need to improve the server here. Maybe we should validate the brlock entry whenever we detect a read/write being blocked from locking? This is not our hot code path anyway, and it would gain us significant robustness. The code might become quite a bit simpler as well.
2012-01-05s3: Clarify what CLEANUP1 doesVolker Lendecke1-1/+2
2012-01-05s3: Add a test excercising the share mode cleanup routineVolker Lendecke1-0/+69