diff options
| author | Martin Schwenke <martin@meltin.net> | 2018-05-15 18:47:29 +1000 |
|---|---|---|
| committer | Amitay Isaacs <amitay@samba.org> | 2018-05-17 04:04:30 +0200 |
| commit | 61efed5a7e19825d49130b4e6785cfb29c557a32 (patch) | |
| tree | 8a0667324c212f63bef061d62cb469f51b17276e /ctdb/config/ctdbd_wrapper | |
| parent | 9193a10f05562c756912d59882eac1cea44bb5d9 (diff) | |
| download | samba-61efed5a7e19825d49130b4e6785cfb29c557a32.tar.gz | |
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>
Diffstat (limited to 'ctdb/config/ctdbd_wrapper')
| -rwxr-xr-x | ctdb/config/ctdbd_wrapper | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/ctdb/config/ctdbd_wrapper b/ctdb/config/ctdbd_wrapper index e8f0a23a257..1642009a69c 100755 --- a/ctdb/config/ctdbd_wrapper +++ b/ctdb/config/ctdbd_wrapper @@ -69,7 +69,6 @@ build_ctdb_options () maybe_set "--no-lmaster" "$CTDB_CAPABILITY_LMASTER" "no" maybe_set "--nosetsched" "$CTDB_NOSETSCHED" "yes" maybe_set "--script-log-level" "$CTDB_SCRIPT_LOG_LEVEL" - maybe_set "--max-persistent-check-errors" "$CTDB_MAX_PERSISTENT_CHECK_ERRORS" } export_debug_variables () |