From: mbroz@sourceware.org <mbroz@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW_DM daemons/dmeventd/libdevmap ...
Date: 15 Jun 2009 12:29:42 -0000 [thread overview]
Message-ID: <20090615122942.3926.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz at sourceware.org 2009-06-15 12:29:41
Modified files:
. : WHATS_NEW_DM
daemons/dmeventd: libdevmapper-event.c
Log message:
Do not fork daemon when dmeventd cannot be found.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.276&r2=1.277
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/daemons/dmeventd/libdevmapper-event.c.diff?cvsroot=lvm2&r1=1.27&r2=1.28
--- LVM2/WHATS_NEW_DM 2009/06/09 16:10:20 1.276
+++ LVM2/WHATS_NEW_DM 2009/06/15 12:29:41 1.277
@@ -1,5 +1,6 @@
Version 1.02.33 -
===============================
+ Do not fork daemon when dmeventd cannot be found.
Add crypt target handling to libdevmapper node.
Add splitname command to dmsetup.
Add subsystem, vg_name, lv_name, lv_layer fields to dmsetup reports.
--- LVM2/daemons/dmeventd/libdevmapper-event.c 2008/11/03 23:01:21 1.27
+++ LVM2/daemons/dmeventd/libdevmapper-event.c 2009/06/15 12:29:41 1.28
@@ -425,6 +425,12 @@
start_server:
/* server is not running */
+
+ if (!strncmp(DMEVENTD_PATH, "/", 1) && stat(DMEVENTD_PATH, &statbuf)) {
+ log_error("Unable to find dmeventd.");
+ return_0;
+ }
+
pid = fork();
if (pid < 0)
next reply other threads:[~2009-06-15 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 12:29 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-10 15:17 LVM2 ./WHATS_NEW_DM daemons/dmeventd/libdevmap zkabelac
2012-02-13 11:24 zkabelac
2012-02-15 13:56 zkabelac
2012-03-12 14:46 zkabelac
2012-03-20 17:38 zkabelac
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=20090615122942.3926.qmail@sourceware.org \
--to=mbroz@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.