Linux Container Development
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
	Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] Add a multi-process IPC test
Date: Sat, 11 Apr 2009 19:48:47 -0400	[thread overview]
Message-ID: <49E12C5F.5020209@cs.columbia.edu> (raw)
In-Reply-To: <20090409185159.GA32610-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>



Serge E. Hallyn wrote:
> Quoting Dan Smith (danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org):
>> This test forks off several children in various states to ensure that the
>> IPC namespace information is properly restored after restart.
> 
> Thanks, Dan.  I've got a few other simple c/r tests collected which I
> want to automate in the next few days so one can just run 'check_cr' and
> get a list of pass/fails.  I'll also add some tests which Nathan had
> written for IPC.  Hmm, I suppose the easiest thing for now will be to
> put a tarball on lxc.sf.net.

I include the c/r tests with the c/r userland tools (ckpt, mktree etc).
That's a natural repository to collect/hold them.

Oren.

> 
> -serge
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
> 

  parent reply	other threads:[~2009-04-11 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 17:46 [PATCH] Add a multi-process IPC test Dan Smith
     [not found] ` <1239299170-14827-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-04-09 17:51   ` Dan Smith
2009-04-09 18:51   ` Serge E. Hallyn
     [not found]     ` <20090409185159.GA32610-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-04-09 18:58       ` Dan Smith
2009-04-11 23:48       ` Oren Laadan [this message]
     [not found]         ` <49E12C5F.5020209-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-04-12 14:20           ` Serge E. Hallyn
2009-04-12  0: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=49E12C5F.5020209@cs.columbia.edu \
    --to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@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