Martin Schwenke b930c885b3 initscript: wait until we can ping ctdbd before setting tunables. ... Currently we do a "sleep 1" after starting and before running set_ctdb_variables to set the tunables. This is too arbitrary and might fail if the system is heavily loaded. This, for example, could result in some nodes running with DeterministicIPs and some without, in which case a different IP allocation algorithm would run depending on who is the recmaster! This makes the start function wait until "ctdb ping" succeeds (with 10 second timeout) before trying to run set_ctdb_variables. If a timeout occurs then the start function attempts to kill ctdbd before exiting with a failure. It also cleans up the status reporting code for Red Hat and SUSE so that the final status code is reported. Currently there are cases where a correct status is prematurely reported before a failure occurs. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit cdcd05662a30b51caaeeab4ac44138cac2474e0a)		2010-08-05 15:29:40 +10:00
..
events.d	Optimise 61.nfstickle to write the tickles more efficiently.	2010-07-30 16:50:18 +10:00
ctdb-crash-cleanup.sh	In the example script to remove all ip addresses after a ctdb crash,	2010-04-23 09:08:26 +10:00
ctdb.init	initscript: wait until we can ping ctdbd before setting tunables.	2010-08-05 15:29:40 +10:00
ctdb.sysconfig	Add a setting where CTDB will monitor and warn for low memory conditions.	2010-04-23 09:08:38 +10:00
functions	config: wrap iptables in flock to avoid concurrancy.	2010-07-15 10:45:24 +09:30
gdb_backtrace	lib/util: import fault/backtrace handling from samba.	2010-01-20 09:44:36 +01:00
interface_modify.sh	config/interface_modify.sh: do the echo before running the script	2010-07-15 15:06:51 +09:30
notify.sh	server: add "setup" event	2010-02-23 10:38:49 +01:00
statd-callout	config: load 'ctdb' config before 'nfs' config in statd-callout	2009-12-16 08:03:55 +01:00