ctdb-scripts: Drop CTDB_MAX_PERSISTENT_CHECK_ERRORS option
authorMartin Schwenke <martin@meltin.net>
Tue, 15 May 2018 08:47:29 +0000 (18:47 +1000)
committerAmitay Isaacs <amitay@samba.org>
Thu, 17 May 2018 02:04:30 +0000 (04:04 +0200)
commit61efed5a7e19825d49130b4e6785cfb29c557a32
tree8a0667324c212f63bef061d62cb469f51b17276e
parent9193a10f05562c756912d59882eac1cea44bb5d9
ctdb-scripts: Drop CTDB_MAX_PERSISTENT_CHECK_ERRORS option

This must harken back to the days of yore when corrupt persistent
databases were an issue.  We haven't seen this used.  If CTDB fails to
start due to a corrupt persistent database then this database can be
removed by hand.

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
ctdb/config/ctdbd_wrapper
ctdb/config/events.d/00.ctdb
ctdb/doc/ctdbd.conf.5.xml