Linux Container Development
 help / color / mirror / Atom feed
From: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: [PATCH] Add --nonetns switch to user-cr checkpoint
Date: Thu, 01 Apr 2010 07:01:51 -0700	[thread overview]
Message-ID: <87wrwrclv4.fsf@caffeine.danplanet.com> (raw)
In-Reply-To: <4BB4240F.2030706-eQaUEPhvms7ENvBUuze7eA@public.gmane.org> (Oren Laadan's message of "Thu\, 01 Apr 2010 00\:41\:51 -0400")

OL> I think the default behavior of 'checkpoint' should be to not
OL> chekcpoint net-ns, at the very least in the subtree-checkpoint
OL> case.

OL> I prefer the container case to also not include it by default.

OL> These can be tuned in the 'checkpoint' utility, or (better ?)
OL> by using CHECKPOINT_NETNS instead of CHECKPOINT_NONETNS...

Okay, so you want to change NONETNS to NETNS and then make user-cr
have a positive flag instead of a negative one, yes?

-- 
Dan Smith
IBM Linux Technology Center
email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org

  parent reply	other threads:[~2010-04-01 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 14:41 [PATCH] Add --nonetns switch to user-cr checkpoint Dan Smith
     [not found] ` <1270046482-16053-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-31 14:57   ` Serge E. Hallyn
     [not found]     ` <20100331145740.GA11124-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-31 15:12       ` Dan Smith
     [not found]         ` <87634ced9n.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-03-31 15:20           ` Serge E. Hallyn
2010-04-01  4:41   ` Oren Laadan
     [not found]     ` <4BB4240F.2030706-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-04-01 14:01       ` Dan Smith [this message]
     [not found]         ` <87wrwrclv4.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-04-01 23:42           ` Oren Laadan

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=87wrwrclv4.fsf@caffeine.danplanet.com \
    --to=danms-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=orenl-eQaUEPhvms7ENvBUuze7eA@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