Move thin_check_executable to proper section

It's read from global section.
In-release change, so no what's new

1 files changed, 15 insertions, 14 deletions

diff --git a/doc/example.conf.in b/doc/example.conf.in
index ad8f2caa..9092e32f 100644
--- a/doc/example.conf.in
+++ b/doc/example.conf.in
@@ -467,6 +467,21 @@ global {
     # proper udev rules, all changes in block device configuration will be
     # *ignored* until a manual 'vgscan' is performed.
     use_lvmetad = 0
+
+    # Full path of the utility called to check that a thin metadata device
+    # is in a state that allows it to be used.
+    # Each time a thin pool needs to be activated or after it is deactivated
+    # this utility is executed. The activation will only proceed if the utility
+    # has an exit status of 0.
+    # Set to "" to skip this check.  (Not recommended.)
+    # The thin tools are available as part of the device-mapper-persistent-data
+    # package from https://github.com/jthornber/thin-provisioning-tools.
+    #
+    thin_check_executable = "@THIN_CHECK_CMD@"
+
+    # String with options passed with thin_check command. By default,
+    # option '-q' is for quiet output.
+    thin_check_options = [ "-q" ]
 }
 
 activation {
@@ -654,20 +669,6 @@ activation {
     thin_pool_autoextend_threshold = 100
     thin_pool_autoextend_percent = 20
 
-    # Full path of the utility called to check that a thin metadata device
-    # is in a state that allows it to be used.
-    # Each time a thin pool needs to be activated, this utility is executed.
-    # The activation will only proceed if the utility has an exit status of 0.
-    # Set to "" to skip this check.  (Not recommended.)
-    # The thin tools are available as part of the device-mapper-persistent-data
-    # package from https://github.com/jthornber/thin-provisioning-tools.
-    #
-    thin_check_executable = "@THIN_CHECK_CMD@"
-
-    # String with options passed with thin_check command. By default,
-    # option '-q' is for quiet output.
-    thin_check_options = [ "-q" ]
-
     # While activating devices, I/O to devices being (re)configured is
     # suspended, and as a precaution against deadlocks, LVM2 needs to pin
     # any memory it is using so it is not paged out.  Groups of pages that