From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Sukadev Bhattiprolu
<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: global_send_sigint
Date: Mon, 10 Jan 2011 20:59:17 -0500 [thread overview]
Message-ID: <4D2BB975.2010306@cs.columbia.edu> (raw)
In-Reply-To: <20100225034746.GA18829-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
At the moment, at least @klogd field has to be set manually.
Perhaps it would be better to provide a pre-initialized struct,
so that users could do:
args = CR_RESTART_ARGS;
or
cr_init_restart_args(&args);
?
Oren
On 02/24/2010 10:47 PM, Sukadev Bhattiprolu wrote:
>
> global_send_sigint is -1 by default.
>
> If it is -1, we either send SIGKILL or SIGINIT depending on whether
> we started "new pidns with init" or "new pidns without init".
>
> If global_send_sigint is explicitly set to 0 by user (--signal is set).
> no signal is sent.
>
> Given that we are making restart() available in libcheckpoint.a, would
> it make sense to switch the behaviors of 0 and -1 ?
>
> i.e if global_send_sigint is 0, send the default signal (SIGINT or SIGKILL).
> If it is -1, then don't send any signal.
>
> That way, applications of restart() (i.e LXC) can simply
>
> memset(&args, 0, sizeof(args))
>
> and get the default behavior. Now they have to explicitly set to -1.
>
> Sukadev
>
next prev parent reply other threads:[~2011-01-11 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 3:47 global_send_sigint Sukadev Bhattiprolu
[not found] ` <20100225034746.GA18829-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2011-01-11 1:59 ` Oren Laadan [this message]
[not found] ` <4D2BB975.2010306-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2011-01-11 21:59 ` global_send_sigint Sukadev Bhattiprolu
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=4D2BB975.2010306@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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