From: Greg Kurz <gkurz@fr.ibm.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: Grzegorz Nosek <root@localdomain.pl>,
containers@lists.linux-foundation.org,
Oleg Nesterov <oleg@redhat.com>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Testing lxc 0.6.5 in Fedora 13
Date: Wed, 24 Mar 2010 10:25:56 +0100 [thread overview]
Message-ID: <1269422756.24051.55.camel@bahia> (raw)
In-Reply-To: <20100323212834.GH20796@count0.beaverton.ibm.com>
On Tue, 2010-03-23 at 14:28 -0700, Matt Helsley wrote:
> On Sun, Mar 21, 2010 at 08:50:44PM +0100, Grzegorz Nosek wrote:
>
> <snip>
>
> > 2. Weird strace behaviour across pidns boundary
> >
> > When strace'ing (with -ff) lxc-start, I get a proper strace for the
> > directly spawned process and the container init. However, any processes
> > spawned by the container's init are not straced properly (I get two
> > empty files, named <foo>.<pid-in-root-ns> and <foo>.2 -- presumably pid
> > inside the container). The container also seems to malfunction under
> > strace (looks like exec() failing as lxc-ps shows two "init" processes).
> >
<snip>
> >
> > 'strace ls' ran completely inside the container works as expected.
>
> I'm suprised strace of ls works across pid namespaces. I've been looking
Matt,
Grzegorz is telling you that 'strace -ff lxc-start ls' is broken but
'lxc-start strace -ff ls' works as expected => strace of ls doesn't work
across pid namespaces. No surprise.
Cheers.
--
Gregory Kurz gkurz@fr.ibm.com
Software Engineer @ IBM/Meiosys http://www.ibm.com
Tel +33 (0)534 638 479 Fax +33 (0)561 400 420
"Anarchy is about taking complete responsibility for yourself."
Alan Moore.
next prev parent reply other threads:[~2010-03-24 9:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100321195044.GA23757@megiteam.pl>
2010-03-23 21:28 ` Testing lxc 0.6.5 in Fedora 13 Matt Helsley
2010-03-24 9:25 ` Greg Kurz [this message]
2010-03-25 21:33 ` Grzegorz Nosek
2010-03-26 11:11 ` Oleg Nesterov
2010-03-26 11:32 ` Grzegorz Nosek
2010-03-26 12:00 ` Oleg Nesterov
2010-03-26 12:46 ` Matt Helsley
2010-03-26 13:34 ` Oleg Nesterov
2010-03-26 11:53 ` Matt Helsley
2010-03-26 12:45 ` Grzegorz Nosek
2010-03-26 12:54 ` Matt Helsley
2010-03-26 13:56 ` Oleg Nesterov
2010-03-26 13:47 ` Oleg Nesterov
2010-04-06 3:44 ` Roland McGrath
2010-04-06 13:53 ` Matt Helsley
2010-04-06 14:36 ` Oleg Nesterov
2010-04-06 15:17 ` Eric W. Biederman
2010-04-06 15:13 ` Eric W. Biederman
2010-04-06 15:29 ` Matt Helsley
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=1269422756.24051.55.camel@bahia \
--to=gkurz@fr.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=root@localdomain.pl \
/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