From b429df90b6db4d9544d01d5cd052e83710acaab0 Mon Sep 17 00:00:00 2001 From: Benjamin Marzinski Date: Fri, 11 Nov 2011 23:12:49 -0600 Subject: [PATCH] multipath: don't print so many add map messages Whenever a dm device gets a change uevent, multipathd prints an add map message. This can get confusing for users, so change that message to not print at the default log level, and add a new message that only prints if multipathd will actually try to add a map Signed-off-by: Benjamin Marzinski --- multipathd/main.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/multipathd/main.c b/multipathd/main.c index 02df98d..920b00a 100644 --- a/multipathd/main.c +++ b/multipathd/main.c @@ -232,7 +232,7 @@ uev_add_map (struct uevent * uev, struct vectors * vecs) char *alias; int major = -1, minor = -1, rc; - condlog(2, "%s: add map (uevent)", uev->kernel); + condlog(3, "%s: add map (uevent)", uev->kernel); alias = uevent_get_dm_name(uev); if (!alias) { condlog(3, "%s: No DM_NAME in uevent", uev->kernel); @@ -280,6 +280,7 @@ ev_add_map (char * dev, char * alias, struct vectors * vecs) } return 0; } + condlog(2, "%s: adding map", alias); /* * now we can register the map -- 2.34.1