Ronnie Sahlberg ef769e7237 track both when we last started and ended a recovery. ... make ctdb uptime print how long the recovery took in the recovery daemon when we check that the public ip address allocation on the local node is correct (we have the ips we should have and we dont have any we shouldnt have) use ctdb uptime and check the recovery start/stop times and make sure we dont check for ip allocation inconsistencies during a recovery where the ip address allocation is in flux. (This used to be ctdb commit f86551580349b7f662f9a07e4eb0c1189e38e429)		2008-07-02 13:55:59 +10:00
..
ctdb_diagnostics	nicer onnode output	2008-01-07 14:31:13 +11:00
ctdb_vacuum.c	add a parameter for the tdb-flags to the client function	2008-06-04 10:46:20 +10:00
ctdb.c	track both when we last started and ended a recovery.	2008-07-02 13:55:59 +10:00
onnode.rsh	allow remote variable expansion in onnode, so you can use wildcards that expand on the remote nodes	2008-01-09 15:04:56 +11:00
onnode.ssh	allow remote variable expansion in onnode, so you can use wildcards that expand on the remote nodes	2008-01-09 15:04:56 +11:00