mirror of
https://github.com/samba-team/samba.git
synced 2024-12-24 21:34:56 +03:00
4b652c1527
This is an optimisation that can cause incorrect results. If ctdbd was killed and there is a stale PID file then this will often cause "CTDB exited during initialisation". The wrapper reads the old PID from the PID file, finds the PID gone, complains and exits. It is better to drop this code and finally get this right. If ctdbd does exit early then it will take CTDB_STARTUP_TIMEOUT (default 10) seconds before the wrapper fails. That's not too bad... Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com> |
||
---|---|---|
.. | ||
events.d | ||
nfs-checks.d | ||
ctdb-crash-cleanup.sh | ||
ctdb.init | ||
ctdb.service | ||
ctdb.sudoers | ||
ctdbd_wrapper | ||
ctdbd.conf | ||
debug_locks.sh | ||
debug-hung-script.sh | ||
functions | ||
gcore_trace.sh | ||
nfs-linux-kernel-callout | ||
notify.d.README | ||
notify.sh | ||
README | ||
statd-callout |
This directory contains run-time support scripts for CTDB. Selected highlights: ctdb.init An initscript for starting ctdbd at boot time. events.d/ Eventscripts. See events.d/README for more details. functions Support functions, sourced by eventscripts and other scripts. statd-callout rpc.statd high-availability callout to support lock migration on failover. Notes: * All of these scripts are written in POSIX Bourne shell. Please avoid bash-isms, including the use of "local" variables (which are not available in POSIX shell). * Do not use absolute paths for commands. Unit tests attempt to replace many commands with stubs and can not do this if commands are specified with absolute paths. The functions file controls $PATH so absolute paths should not be required.