Linux Device Mapper development
 help / color / mirror / Atom feed
From: agk@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: device-mapper/dmeventd dmeventd.c
Date: 19 Jan 2007 18:08:37 -0000	[thread overview]
Message-ID: <20070119180837.25196.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/dm
Module name:	device-mapper
Changes by:	agk@sourceware.org	2007-01-19 18:08:37

Modified files:
	dmeventd       : dmeventd.c 

Log message:
	fix exit status; always print message on child failure

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/dmeventd/dmeventd.c.diff?cvsroot=dm&r1=1.41&r2=1.42

--- device-mapper/dmeventd/dmeventd.c	2007/01/19 17:22:17	1.41
+++ device-mapper/dmeventd/dmeventd.c	2007/01/19 18:08:36	1.42
@@ -1558,22 +1558,19 @@
 		/* Problem with child.  Determine what it is by exit code */
 		switch (WEXITSTATUS(child_status)) {
 		case EXIT_LOCKFILE_INUSE:
+			fprintf(stderr, "Another dmeventd daemon is already running\n");
 			break;
 		case EXIT_DESC_CLOSE_FAILURE:
-			break;
 		case EXIT_DESC_OPEN_FAILURE:
-			break;
 		case EXIT_OPEN_PID_FAILURE:
-			break;
 		case EXIT_FIFO_FAILURE:
-			break;
 		case EXIT_CHDIR_FAILURE:
-			break;
 		default:
+			fprintf(stderr, "Child exited with code %d\n", WEXITSTATUS(child_status));
 			break;
 		}
 
-		exit(child_status);
+		exit(WEXITSTATUS(child_status));
 	}
 
 	if (chdir("/"))

             reply	other threads:[~2007-01-19 18:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 18:08 agk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-09 13:26 device-mapper/dmeventd dmeventd.c mornfall
2007-04-24 13:29 mornfall
2007-01-16 20:27 agk
2007-01-16 20:13 agk
2007-01-15 22:37 agk
2007-01-15 19:19 agk
2007-01-15 18:58 agk

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=20070119180837.25196.qmail@sourceware.org \
    --to=agk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox