All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marian Csontos <mcsontos@sourceware.org>
To: lvm-devel@redhat.com
Subject: main - make: generate
Date: Fri,  5 Mar 2021 12:01:47 +0000 (GMT)	[thread overview]
Message-ID: <20210305120147.3BCCB3870902@sourceware.org> (raw)

Gitweb:        https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=2244a56021475179b8cc3633c8cb6534eaa18025
Commit:        2244a56021475179b8cc3633c8cb6534eaa18025
Parent:        3bea8937334ab9a7852947a30862d6e457f093b6
Author:        Marian Csontos <mcsontos@redhat.com>
AuthorDate:    Fri Mar 5 12:53:35 2021 +0100
Committer:     Marian Csontos <mcsontos@redhat.com>
CommitterDate: Fri Mar 5 12:53:35 2021 +0100

make: generate

---
 conf/example.conf.in | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/conf/example.conf.in b/conf/example.conf.in
index 8ac376303..204ec82d1 100644
--- a/conf/example.conf.in
+++ b/conf/example.conf.in
@@ -1122,6 +1122,17 @@ global {
 	# This configuration option has an automatic default value.
 	# sanlock_lv_extend = 256
 
+	# Configuration option global/lvmlockctl_kill_command.
+	# The command that lvmlockctl --kill should use to force LVs offline.
+	# The lvmlockctl --kill command is run when a shared VG has lost
+	# access to locks (e.g. when sanlock has lost access to storage.)
+	# An empty string means that there will be no automatic attempt by
+	# lvmlockctl --kill to forcibly shut down LVs in the VG, and the user
+	# can manually intervene as described in lvmlockd(8).
+	# The VG name will be appended to the command specified here.
+	# This configuration option has an automatic default value.
+	# lvmlockctl_kill_command = ""
+
 	# Configuration option global/thin_check_executable.
 	# The full path to the thin_check command.
 	# LVM uses this command to check that a thin metadata device is in a



             reply	other threads:[~2021-03-05 12:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 12:01 Marian Csontos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-23 16:09 main - make: generate Zdenek Kabelac
2023-03-22 12:44 Tony Asleson
2023-03-21 12:39 Marian Csontos
2022-11-10 13:22 Marian Csontos
2022-09-21 12:59 Zdenek Kabelac
2022-08-11 11:06 Peter Rajnoha
2022-07-10 23:22 Zdenek Kabelac
2022-05-18 16:15 Marian Csontos
2022-05-03 17:11 Zdenek Kabelac
2022-02-07 19:03 Zdenek Kabelac
2021-10-14 21:37 Zdenek Kabelac
2021-10-07 17:43 David Teigland
2021-09-23 14:52 Zdenek Kabelac
2021-08-09 14:27 Marian Csontos
2021-05-07 15:45 Marian Csontos
2021-04-23 21:06 Zdenek Kabelac
2021-04-19 13:01 Zdenek Kabelac
2021-04-12  9:13 Zdenek Kabelac
2021-04-12  7:55 Zdenek Kabelac
2021-03-19 23:17 Zdenek Kabelac
2021-03-02 21:58 Zdenek Kabelac
2021-02-17 10:54 Zdenek Kabelac
2021-01-18 13:46 Marian Csontos

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=20210305120147.3BCCB3870902@sourceware.org \
    --to=mcsontos@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.