public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: zkabelac@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW_DM daemons/dmeventd/libdevmap ...
Date: Mon, 12 Mar 2012 14:46:00 -0000 [thread overview]
Message-ID: <20120312144654.31151.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac@sourceware.org 2012-03-12 14:46:53
Modified files:
. : WHATS_NEW_DM
daemons/dmeventd: libdevmapper-event.c
Log message:
We need longer window for checking read from fifo.
Seems like some dmeventd startups are taking more time then expected,
so make the time window longer here.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.591&r2=1.592
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/daemons/dmeventd/libdevmapper-event.c.diff?cvsroot=lvm2&r1=1.48&r2=1.49
--- LVM2/WHATS_NEW_DM 2012/03/06 04:47:37 1.591
+++ LVM2/WHATS_NEW_DM 2012/03/12 14:46:53 1.592
@@ -1,5 +1,6 @@
Version 1.02.75 -
================================
+ Make the time window for reading fifo longer 5sec (1.02.73).
Version 1.02.74 - 6th March 2012
================================
--- LVM2/daemons/dmeventd/libdevmapper-event.c 2012/03/01 10:41:48 1.48
+++ LVM2/daemons/dmeventd/libdevmapper-event.c 2012/03/12 14:46:53 1.49
@@ -245,7 +245,7 @@
log_error("Unable to read from event server");
return 0;
}
- if ((ret == 0) && i && !bytes) {
+ if ((ret == 0) && (i > 4) && !bytes) {
log_error("No input from event server.");
return 0;
}
next reply other threads:[~2012-03-12 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 14:46 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-20 17:38 zkabelac
2012-02-15 13:56 zkabelac
2012-02-13 11:24 zkabelac
2012-02-10 15:17 zkabelac
2009-06-15 12:29 mbroz
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=20120312144654.31151.qmail@sourceware.org \
--to=zkabelac@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).