All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: kt-S89nZTSLPHGGdvJs77BJ7Q@public.gmane.org
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	lxc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [patch 1/4][resend] fuse-procfs: proxy proc files
Date: Mon, 28 Sep 2009 17:47:51 +0200	[thread overview]
Message-ID: <4AC0DAA7.9090907@free.fr> (raw)
In-Reply-To: <ac1c4bf20909280233r5cd94343m30ac00c6ef9e1d10-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Krzysztof Taraszka wrote:
> Thank you Daniel.
> I have a little problem with fuse and containers. Do I have to add the fuse
> device to the container?
> When I tried to mount procfs I received:
>
> container2:/# ./procfs -odirect_io /proc/meminfo
> fuse: device not found, try 'modprobe fuse' first
>
> The fuse module was loaded on host. What I did wrong? I am asking because I
> am working around user space scripts for managing lxc (written in bash,
> init.d script, few lxc-create-* scripts based on distro, etc) and I would
> like to add this development future to this scripts.
> Right now I have few nice and good looking userspace scripts.
> Would be great If I may do the deb and rpm package with lxc user scripts and
> lxc-tools or add my scripts to lxc-tools tree.
>   
Let's see :)

> More about that in this week in the different thread. Hope you will give me
> the direction guys.
>   

I think the command line is not right. Fuse uses at the /proc directory 
when initializating, so that have to be done in two steps:

Can you try:

lxc-execute -n foo /bin/bash

(from the shell in the container):
procfs -o direct_io /tmp/<tmpdir>
mount --bind /tmp/<tmpdir> /proc
echo 268435456 > /cgroup/foo/memory.memsw.limit_in_bytes
echo 268435456 > /cgroup/foo/memory.limit_in_bytes

* before exiting the container:
umount /proc
fusermount -u /tmp/<tmpfile>

If you do 'ls /proc', you should see everything expect the /proc/sys 
directory.
If you do 'cat /proc/meminfo', you should see:
MemTotal: 262144 kB
MemFree: 250684 kB
SwapTotal: 262144 kB
SwapFree: 0 kB

      parent reply	other threads:[~2009-09-28 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090904162556.407556958@mai-009101017029.toulouse-stg.fr.ibm.com>
     [not found] ` <20090904165149.491603361@mai-009101017029.toulouse-stg.fr.ibm.com>
     [not found]   ` <20090904165149.491603361-+lpkiSBCrgqwGcPS5fe+fxcU4LlsiAD9x8DZ0lRKBDr1ENwx4SLHqw@public.gmane.org>
2009-09-11  2:57     ` [patch 1/4][resend] fuse-procfs: proxy proc files Serge E. Hallyn
2009-09-14 20:38     ` Krzysztof Taraszka
     [not found]       ` <ac1c4bf20909141338p3e13c1d6sc71899b7859bd963-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-14 21:13         ` Daniel Lezcano
     [not found]           ` <4AAEB1FA.3070102-GANU6spQydw@public.gmane.org>
2009-09-28  9:33             ` Krzysztof Taraszka
     [not found]               ` <ac1c4bf20909280233r5cd94343m30ac00c6ef9e1d10-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-28 15:47                 ` Daniel Lezcano [this message]

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=4AC0DAA7.9090907@free.fr \
    --to=daniel.lezcano-ganu6spqydw@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=kt-S89nZTSLPHGGdvJs77BJ7Q@public.gmane.org \
    --cc=lxc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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.