From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: commit 7534432dcc3c654a8671b6b0cdffd1dbdbc73074
Date: Thu, 22 Jan 2009 20:06:03 -0600 [thread overview]
Message-ID: <20090123020603.GA9267@us.ibm.com> (raw)
In-Reply-To: <6599ad830901221507x796c154ck5fe4f95cc3eb8e0e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Quoting Paul Menage (menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org):
> On Thu, Jan 22, 2009 at 10:47 AM, Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> wrote:
> > #!/bin/bash
> > mount -t cgroup -o freezer none /cgroup
> > sleep 100 &
> > pid=`jobs -p`
>
> You can use $! to refer to the most recently started background process.
Hah - thanks, I actually looked for something like that but couldn't
find it.
>
> > mkdir /cgroup/1
> > echo $pid > /cgroup/1/tasks
> > umount /cgroup
> > mount -t cgroup -o freezer,ns none /cgroup
>
> This command should have failed with EBUSY, since freezer is already
> part of an existing hierarchy. So I think it's a red herring in this
> problem.
>
> > mount -t cgroup -o freezer none /cgroup
> > #kill %1
>
> Is there a reason for this commented-out line?
Sorry, I'd meant to look into whether that needed
to be there or not, but decided to put it off until
after git bisecting, then forgot, probably because
the bisect result was so confusing.
I see you already sent a patch for the *real*
problem, thanks!
-serge
next prev parent reply other threads:[~2009-01-23 2:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 18:47 commit 7534432dcc3c654a8671b6b0cdffd1dbdbc73074 Serge E. Hallyn
[not found] ` <20090122184754.GA17511-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-01-22 23:07 ` Paul Menage
[not found] ` <6599ad830901221507x796c154ck5fe4f95cc3eb8e0e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-22 23:35 ` Paul Menage
[not found] ` <6599ad830901221535w6c723eb6xd0adced0ff6a1fb6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-23 0:26 ` Paul Menage
[not found] ` <6599ad830901221626o2fd5025fib3c1c6d182e52e63-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-23 1:26 ` Matt Helsley
2009-01-23 1:31 ` Paul Menage
2009-01-23 2:06 ` Serge E. Hallyn [this message]
2009-01-23 1:12 ` Paul Menage
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=20090123020603.GA9267@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.