From: Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH 2/2] have restart return error if error
Date: Fri, 16 Oct 2009 20:15:52 -0400 [thread overview]
Message-ID: <4AD90CB8.5050307@librato.com> (raw)
In-Reply-To: <20091015184935.GB30490-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Serge E. Hallyn wrote:
> I still need this for cr_tests/userns/run_simple.sh to succeed.
> All tests pass with this patch applied.
>
But this is not the intended behavior.
The coordinator will:
1) If restart fails, exit with an error status (>0)
2) If restart succeeds, exit immediately with status 0 (--no-wait),
or (by default) wait for the restart root-task to exit, and then
exit with success status 0, regardless of the exit status (or
reason) of the restarted root-task.
What you want is that the coordinator instead will report the exit
status of the restart root-task. You can use the --copy-status
command line switch for that.
The intended behavior is that if the restarted root-task died due
to a signal, then so will the coordinator (if --copy-status is
requested). I now see that this part needs a small fix - to ensure
that the signal is not handled by the coordinator. Will fix that.
Oren.
> Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> ---
> restart.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/restart.c b/restart.c
> index cb81293..fa786ef 100644
> --- a/restart.c
> +++ b/restart.c
> @@ -780,7 +780,7 @@ static int ckpt_parse_status(int status, int mimic, int verbose)
> }
> }
>
> - return 0;
> + return ret;
> }
>
> static int ckpt_collect_child(struct ckpt_ctx *ctx)
next prev parent reply other threads:[~2009-10-17 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 18:49 [PATCH 2/2] have restart return error if error Serge E. Hallyn
[not found] ` <20091015184935.GB30490-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-17 0:15 ` Oren Laadan [this message]
[not found] ` <4AD90CB8.5050307-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-10-17 5:17 ` Serge E. Hallyn
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=4AD90CB8.5050307@librato.com \
--to=orenl-rdfvbdnroixbdgjk7y7tuq@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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