Ronnie sahlberg 18595074d3 add code to fetch1 test to tell the two child processes one at a time to fetch_lock the same record ... they both successfully fetch and lock the same record at this stage but when the actual locking works properly the second child will block. this test allows us to verify the blocking once we have implemented it (This used to be ctdb commit b1c0baa03a669757aaacb6e1a2794224f5ba2cd7)		2007-04-16 08:37:27 +10:00
..
1node.txt	- added a 1 node test	2006-12-01 10:23:03 +11:00
4nodes.txt	added a 4 node test	2006-12-18 16:05:22 +11:00
bench1.sh	merge fetch code from ronnie, and add a simple fetch test	2007-04-05 13:18:31 +10:00
bench-ssh.sh	added a benchmark script that launches via ssh	2007-02-20 13:23:01 +11:00
bench.sh	add a test that sends messages between clients connected to the same ctdb	2007-04-11 13:43:15 +10:00
ctdb_bench.c	private -> private_data for samba3	2007-04-13 20:38:24 +10:00
ctdb_fetch1.c	add code to fetch1 test to tell the two child processes one at a time to fetch_lock the same record	2007-04-16 08:37:27 +10:00
ctdb_fetch.c	private -> private_data for samba3	2007-04-13 20:38:24 +10:00
ctdb_messaging.c	private -> private_data for samba3	2007-04-13 20:38:24 +10:00
ctdb_test.c	add a CONNECT_WAIT flag to replace the call ctdb_connect_wait() since	2007-04-10 12:18:58 +10:00
fetch1.sh	add the two missing file from the previous commit	2007-04-12 21:19:00 +10:00
fetch.sh	dont hardcode gdb in the test script. ooops	2007-04-12 16:49:37 +10:00
messaging.sh	add a test that sends messages between clients connected to the same ctdb	2007-04-11 13:43:15 +10:00
nodes.txt	fixed a bunch of memory leaks	2007-04-07 10:45:00 +10:00
test1.sh	make normal/deamon mode controllable by a ctdb flag so that the api looks the same in both modes to a client.	2007-04-10 06:03:39 +10:00
test.sh	restore the test script that was updated by mistake in the previous checkin	2007-04-10 12:23:10 +10:00