Linux Device Mapper development
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: christophe.varoqui@opensvc.com
Cc: device-mapper development <dm-devel@redhat.com>,
	Christophe Varoqui <christophe.varoqui@gmail.com>
Subject: Re: [PATCH] multipath: change default configuration parameters
Date: Tue, 15 Jan 2013 22:48:29 +0100	[thread overview]
Message-ID: <50F5CEAD.8070809@gmail.com> (raw)
In-Reply-To: <1358283765.3854.1.camel@lapoo.opensvc.com>

On 01/15/2013 10:02 PM, Christophe Varoqui wrote:

> I pushed a patch to resync the multipath.conf.defaults using the
> "multipathd show config" output.

> --- a/multipath.conf.defaults
> +++ b/multipath.conf.defaults
> @@ -2,775 +2,863 @@
>  # overwrite these values in your config file.
>  
>  #defaults {
> -#      udev_dir                /dev
> -#      polling_interval        5
> -#      path_selector           "round-robin 0"
> -#      path_grouping_policy    failover
> -#      getuid_callout          "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
> -#      prio                    const
> -#      prio_args               ""
> -#      path_checker            directio
> -#      rr_min_io               1000
> -#      rr_weight               uniform
> -#      failback                manual
> -#      no_path_retry           fail
> -#      user_friendly_names     no
> +#      verbosity 2
> +#      polling_interval 5
> +#      multipath_dir "/lib64/multipath"

multipath_dir should be removed, it's generated at compile time.

  reply	other threads:[~2013-01-15 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  5:34 [PATCH] multipath: change default configuration parameters Benjamin Marzinski
2013-01-10 17:33 ` Xose Vazquez Perez
2013-01-15 21:02   ` Christophe Varoqui
2013-01-15 21:48     ` Xose Vazquez Perez [this message]
2013-01-16 20:42       ` Christophe Varoqui
2013-01-15 22:14     ` Xose Vazquez Perez
2013-01-16 21:24       ` Christophe Varoqui
2013-01-17  7:30         ` Hannes Reinecke

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=50F5CEAD.8070809@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=christophe.varoqui@gmail.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox