All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@sourceware.org>
To: lvm-devel@redhat.com
Subject: main - lvm.conf: remove reference to locking_type
Date: Tue, 17 Nov 2020 17:21:01 +0000 (GMT)	[thread overview]
Message-ID: <20201117172101.1D69E386F005@sourceware.org> (raw)

Gitweb:        https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=b68141a49d94db7fa98beb345bc5a583d874e9e7
Commit:        b68141a49d94db7fa98beb345bc5a583d874e9e7
Parent:        9c0253d930103c33784fac5b303da20104a314b6
Author:        David Teigland <teigland@redhat.com>
AuthorDate:    Tue Nov 17 11:19:55 2020 -0600
Committer:     David Teigland <teigland@redhat.com>
CommitterDate: Tue Nov 17 11:19:55 2020 -0600

lvm.conf: remove reference to locking_type

---
 lib/config/config_settings.h | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/lib/config/config_settings.h b/lib/config/config_settings.h
index e4e3dcdde..163e01485 100644
--- a/lib/config/config_settings.h
+++ b/lib/config/config_settings.h
@@ -982,8 +982,7 @@ cfg(global_prioritise_write_locks_CFG, "prioritise_write_locks", global_CFG_SECT
 	"a volume group's metadata, instead of always granting the read-only\n"
 	"requests immediately, delay them to allow the read-write requests to\n"
 	"be serviced. Without this setting, write access may be stalled by a\n"
-	"high volume of read-only requests. This option only affects\n"
-	"locking_type 1 viz. local file-based locking.\n")
+	"high volume of read-only requests. This option only affects file locks.\n")
 
 cfg(global_library_dir_CFG, "library_dir", global_CFG_SECTION, CFG_DEFAULT_UNDEFINED, CFG_TYPE_STRING, NULL, vsn(1, 0, 0), NULL, 0, NULL,
 	"Search this directory first for shared libraries.\n")



                 reply	other threads:[~2020-11-17 17:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201117172101.1D69E386F005@sourceware.org \
    --to=teigland@sourceware.org \
    --cc=lvm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.