Hi,
I see in conf.c that a .hold file is automatically created whenever you use a
directory as the rootfs. I'm seeing those start to accumulate on the
filesystem. Is it my job to clean them up, or should there be code in LXC
deleting them when the container shuts down?
Thanks,
Brent
Brent T
Hi,
I tried to put lxc.cgroup.memory.kmem.limit_in_bytes = 4194304 in a
config file to test forkbomb prevention. The problem with this is that
kmem.limit_in_bytes (per the kernel documentation) "cannot be set if
the cgroup have children, or if there are already tasks in the cgroup".
Currently, lxc
Signed-off-by: Dwight Engen
---
src/lxc/conf.c | 37 -
src/lxc/conf.h | 2 ++
src/lxc/start.c | 5 +
3 files changed, 39 insertions(+), 5 deletions(-)
diff --git a/src/lxc/conf.c b/src/lxc/conf.c
index 746a2db..6a9b493 100644
--- a/src/lxc/conf.c
+++ b
Quoting Dwight Engen (dwight.en...@oracle.com):
> The problem is that the fd table is shared between threads and if a thread
> forks() while another thread has an open fd to the monitor, the duped fd
> in the fork()ed child will not get closed, thus causing monitord to stay
> around since it thinks
The problem is that the fd table is shared between threads and if a thread
forks() while another thread has an open fd to the monitor, the duped fd
in the fork()ed child will not get closed, thus causing monitord to stay
around since it thinks it still has a client. This only happened when
calling
Quoting Purcareata Bogdan-B43198 (b43...@freescale.com):
> Hello,
>
> Should lxc-ls list containers created with lxc-execute as well?
>
> E.g. when running "lxc-execute -n ctx1 /bin/bash", you may run "lxc-info -n
> ctx1" and it will output
>
> state: RUNNING
> pid: 4063
>
> but when is
Hello,
Should lxc-ls list containers created with lxc-execute as well?
E.g. when running "lxc-execute -n ctx1 /bin/bash", you may run "lxc-info -n
ctx1" and it will output
state: RUNNING
pid: 4063
but when issuing "lxc-ls", nothing will be printed. Is this normal? I noticed
that the co
Hello,
Should lxc-ls list containers created with lxc-execute as well?
E.g. when running "lxc-execute -n ctx1 /bin/bash", you may run "lxc-info -n
ctx1" and it will output
state: RUNNING
pid: 4063
but when issuing "lxc-ls", nothing will be printed. Is this normal? I noticed
that the co
