mirror of
https://github.com/samba-team/samba.git
synced 2025-03-15 02:50:27 +03:00
82e7f38214
ctdbd will start without a recovery lock configured. It will log a message saying that this is not optimal. However, a careless user may overlook both this message and the importance of setting a recovery lock. If the existing example configuration is uncommented then the directory containing it will be created (by 01.reclock.script) and the failure (i.e. multiple nodes able to take the lock) will be confusing. Instead, change the example setting to one that will result in banned nodes, encouraging users to consciously configure (or deconfigure) the recovery lock. Tweak the corresponding comment. BUG: https://bugzilla.samba.org/show_bug.cgi?id=13790 Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
This directory contains run-time support scripts for CTDB.
Selected highlights:
ctdb.init
An initscript for starting ctdbd at boot time.
events/
Eventscripts. See events/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.