mirror of
https://github.com/samba-team/samba.git
synced 2024-12-22 13:34:15 +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>
23 lines
555 B
Plaintext
23 lines
555 B
Plaintext
# See ctdb.conf(5) for documentation
|
|
#
|
|
# See ctdb-script.options(5) for documentation about event script
|
|
# options
|
|
|
|
[logging]
|
|
# Enable logging to syslog
|
|
# location = syslog
|
|
|
|
# Default log level
|
|
# log level = NOTICE
|
|
|
|
[cluster]
|
|
# Shared recovery lock file to avoid split brain. Daemon
|
|
# default is no recovery lock. Do NOT run CTDB without a
|
|
# recovery lock file unless you know exactly what you are
|
|
# doing.
|
|
#
|
|
# Please see the RECOVERY LOCK section in ctdb(7) for more
|
|
# details.
|
|
#
|
|
# recovery lock = !/bin/false RECOVERY LOCK NOT CONFIGURED
|