From 14e815eedecb824e86ca6cb512724840d6002ef0 Mon Sep 17 00:00:00 2001 From: Phil Watts Date: Wed, 15 Feb 2017 11:09:27 -0500 Subject: [PATCH] Edit to the language of the description of disable_mlock on the configuration documentation page. Previous wording could lead to confusion as to the recommended setting of the disable_mlock option. (#2377) --- website/source/docs/config/index.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/config/index.html.md b/website/source/docs/config/index.html.md index a991178054..7aa1681e7a 100644 --- a/website/source/docs/config/index.html.md +++ b/website/source/docs/config/index.html.md @@ -64,8 +64,8 @@ sending a SIGHUP to the server process. These are denoted below. subsystem. This will very significantly impact performance. * `disable_mlock` (optional) - A boolean. If true, this will disable the - server from executing the `mlock` syscall to prevent memory from being - swapped to disk. This is not recommended in production (see below). + server from executing the `mlock` syscall. `mlock` prevents memory from being + swapped to disk. Disabling `mlock` is not recommended in production (see below). * `telemetry` (optional) - Configures the telemetry reporting system (see below).