All of lore.kernel.org
 help / color / mirror / Atom feed
From: bmarzins@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: multipath-tools ./multipath.conf.defaults libm ...
Date: 21 Jan 2011 16:57:45 -0000	[thread overview]
Message-ID: <20110121165745.25363.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/dm
Module name:	multipath-tools
Branch: 	RHEL4_FC5
Changes by:	bmarzins@sourceware.org	2011-01-21 16:57:44

Modified files:
	.              : multipath.conf.defaults 
	libmultipath   : hwtable.c 

Log message:
	Remove old config entry, and update multipath.conf.defaults

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/multipath.conf.defaults.diff?cvsroot=dm&only_with_tag=RHEL4_FC5&r1=1.5.2.13&r2=1.5.2.14
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/libmultipath/hwtable.c.diff?cvsroot=dm&only_with_tag=RHEL4_FC5&r1=1.16.2.18&r2=1.16.2.19

--- multipath-tools/multipath.conf.defaults	2009/09/11 15:19:50	1.5.2.13
+++ multipath-tools/multipath.conf.defaults	2011/01/21 16:57:43	1.5.2.14
@@ -87,9 +87,9 @@
 #               vendor                  "HP"
 #               product                 "HSVX700"
 #               path_grouping_policy    group_by_prio
-#               prio_callout            "/sbin/mpath_prio_alua /dev/%n"
-#		hardware_handler	"1 alua"
-#               path_checker            tur
+#               prio_callout            "/sbin/mpath_prio_hp_sw /dev/%n"
+#		hardware_handler	"0"
+#               path_checker            hp_sw
 #		failback		immediate
 #               no_path_retry           12
 #		rr_min_io		100
--- multipath-tools/libmultipath/hwtable.c	2010/10/27 18:55:55	1.16.2.18
+++ multipath-tools/libmultipath/hwtable.c	2011/01/21 16:57:44	1.16.2.19
@@ -54,10 +54,6 @@
 			   GROUP_BY_PRIO, DEFAULT_GETUID,
 			   "/sbin/mpath_prio_alua /dev/%n", "0", "0", "tur",
 			   -FAILBACK_IMMEDIATE, NULL, 18, 0, 100);
-        r += store_hwe_ext(hw, "HP", "HSVX700",
-			   GROUP_BY_PRIO, DEFAULT_GETUID,
-			   "/sbin/mpath_prio_alua /dev/%n", "1 alua", "0",
-			   "tur", -FAILBACK_IMMEDIATE, NULL, 12, 0, 100);
 	r += store_hwe_ext(hw, "HP", "MSA2000s*", MULTIBUS, "/sbin/cciss_id %n",
 	                   NULL, "0", "0", "cciss_tur", FAILBACK_UNDEF, NULL,
 	                   12, 0, 0);

             reply	other threads:[~2011-01-21 16:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 16:57 bmarzins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-14 21:56 multipath-tools ./multipath.conf.defaults libm bmarzins
2010-11-12 20:17 bmarzins
2010-09-21 18:06 bmarzins
2010-09-14 19:42 bmarzins
2010-09-03  3:46 bmarzins
2010-08-24 21:51 bmarzins
2010-08-09 21:35 bmarzins
2010-08-09 18:38 bmarzins
2010-02-10  4:11 bmarzins
2010-01-26  5:50 bmarzins
2009-12-02 19:15 bmarzins
2009-09-28 18:41 bmarzins
2009-09-28 18:28 bmarzins
2009-09-11 15:19 bmarzins
2009-08-19 21:52 bmarzins
2009-01-15 22:47 bmarzins
2009-01-13 22:26 bmarzins
2008-08-29 18:30 bmarzins
2008-07-12 17:36 bmarzins
2008-07-12  2:44 bmarzins
2008-07-12  0:07 bmarzins
2008-01-03 20:16 bmarzins
2007-10-09 21:48 bmarzins
2007-09-11 18:06 bmarzins
2007-08-14 18:08 bmarzins
2007-08-14 18:23 ` S. J. van Harmelen
2007-05-07 17:59 bmarzins
2006-12-19 22:51 bmarzins

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=20110121165745.25363.qmail@sourceware.org \
    --to=bmarzins@sourceware.org \
    --cc=dm-cvs@sourceware.org \
    --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 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.