xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: rshriram@cs.ubc.ca
To: xen-devel@lists.xensource.com
Cc: anthony.perard@citrix.com, brendan@cs.ubc.ca,
	ian.jackson@eu.citrix.com, ian.campbell@citrix.com
Subject: [PATCH 2 of 6] libxl: bugfix: create_domain() return to caller if	!daemonize
Date: Mon, 30 Jan 2012 17:05:07 -0800	[thread overview]
Message-ID: <39f63438767a8225a314.1327971907@athos.nss.cs.ubc.ca> (raw)
In-Reply-To: <patchbomb.1327971905@athos.nss.cs.ubc.ca>

# HG changeset patch
# User Shriram Rajagopalan <rshriram@cs.ubc.ca>
# Date 1327971504 28800
# Node ID 39f63438767a8225a3148a43139c10f55a62c669
# Parent  20bbc4a754a701ef14c9136a1adffc1c90bc1f4a
libxl: bugfix: create_domain() return to caller if !daemonize

Currently the create_domain function does not honor
the daemonize flag properly. It exits irrespective of
the value of the flag. This patch fixes the issue.

Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca>

diff -r 20bbc4a754a7 -r 39f63438767a tools/libxl/xl_cmdimpl.c
--- a/tools/libxl/xl_cmdimpl.c	Mon Jan 30 16:58:13 2012 -0800
+++ b/tools/libxl/xl_cmdimpl.c	Mon Jan 30 16:58:24 2012 -0800
@@ -1814,7 +1814,7 @@ waitpid_out:
      * If we have daemonized then do not return to the caller -- this has
      * already happened in the parent.
      */
-    if ( !need_daemon )
+    if ( daemonize && !need_daemon )
         exit(ret);
 
     return ret;

  parent reply	other threads:[~2012-01-31  1:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31  1:05 [PATCH 0 of 6] libxl: refactor suspend/resume code rshriram
2012-01-31  1:05 ` [PATCH 1 of 6] libxl: helper function to send commands to traditional qemu rshriram
2012-01-31  9:46   ` Ian Campbell
2012-01-31 17:30     ` Shriram Rajagopalan
2012-02-09 18:08       ` Ian Jackson
2012-01-31  1:05 ` rshriram [this message]
2012-01-31  9:47   ` [PATCH 2 of 6] libxl: bugfix: create_domain() return to caller if !daemonize Ian Campbell
2012-02-09 18:06     ` Ian Jackson
2012-01-31  1:05 ` [PATCH 3 of 6] libxl: QMP stop/resume & refactor QEMU suspend/resume/save rshriram
2012-01-31  9:54   ` Ian Campbell
2012-01-31 17:32     ` Shriram Rajagopalan
2012-01-31 23:53       ` Shriram Rajagopalan
2012-02-01 10:46         ` Ian Campbell
2012-01-31  1:05 ` [PATCH 4 of 6] libxl: support suspend_cancel in domain_resume rshriram
2012-01-31 10:00   ` Ian Campbell
2012-01-31 10:04     ` Ian Campbell
2012-01-31 17:52     ` Shriram Rajagopalan
2012-02-01 10:47       ` Ian Campbell
2012-02-01 10:53       ` Ian Campbell
2012-02-01 15:48         ` Pasi Kärkkäinen
2012-02-01 16:02           ` Ian Campbell
2012-02-01 19:30             ` Shriram Rajagopalan
2012-02-02  7:04               ` Shriram Rajagopalan
2012-02-02  7:59                 ` Ian Campbell
2012-02-02  7:58               ` Ian Campbell
2012-01-31  1:05 ` [PATCH 5 of 6] libxl: refactor migrate_domain and generalize migrate_receive rshriram
2012-01-31 10:19   ` Ian Campbell
2012-01-31  1:05 ` [PATCH 6 of 6] libxl: resume instead of unpause on xl save -c rshriram
2012-01-31 10:21   ` Ian Campbell
2012-01-31 17:55     ` Shriram Rajagopalan

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=39f63438767a8225a314.1327971907@athos.nss.cs.ubc.ca \
    --to=rshriram@cs.ubc.ca \
    --cc=anthony.perard@citrix.com \
    --cc=brendan@cs.ubc.ca \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).