0afef53a17
Today if system call filters fail to install on startup, we log a message but otherwise march on. This might leave users without system call filters installed not knowing that they have implicitly accepted the additional risk. We should not be lenient like this, instead clearly informing the user that they have to either fix their configuration or accept the risk of not having system call filters installed. This commit adds a bootstrap check that if system call filters are enabled, they must successfully install. Relates #21940 |
||
---|---|---|
.. | ||
install | ||
sysconfig | ||
bootstrap-checks.asciidoc | ||
cluster_restart.asciidoc | ||
configuration.asciidoc | ||
important-settings.asciidoc | ||
install.asciidoc | ||
reindex_upgrade.asciidoc | ||
rolling_upgrade.asciidoc | ||
stopping.asciidoc | ||
sysconfig.asciidoc | ||
upgrade.asciidoc |