mirror of
https://github.com/samba-team/samba.git
synced 2024-12-22 13:34:15 +03:00
ctdb-config: Change example recovery lock setting to one that fails
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 commit is contained in:
parent
12da33e2bb
commit
82e7f38214
@ -11,7 +11,12 @@
|
|||||||
# log level = NOTICE
|
# log level = NOTICE
|
||||||
|
|
||||||
[cluster]
|
[cluster]
|
||||||
# Shared recovery lock file to avoid split brain. No default.
|
# Shared recovery lock file to avoid split brain. Daemon
|
||||||
# Do NOT run CTDB without a recovery lock file unless you know exactly
|
# default is no recovery lock. Do NOT run CTDB without a
|
||||||
# what you are doing.
|
# recovery lock file unless you know exactly what you are
|
||||||
# recovery lock = /shared/recovery.lock
|
# doing.
|
||||||
|
#
|
||||||
|
# Please see the RECOVERY LOCK section in ctdb(7) for more
|
||||||
|
# details.
|
||||||
|
#
|
||||||
|
# recovery lock = !/bin/false RECOVERY LOCK NOT CONFIGURED
|
||||||
|
Loading…
Reference in New Issue
Block a user