Daniel Lezcano daniel.lezc...@free.fr writes:
On 06/09/2010 07:56 PM, Ferenc Wagner wrote:
here are basically the same patches, with some obvious errors corrected
and some unrelated documentation added. It actually survived some
targeted testing in the past days and seems to behave as
On 07/15/2010 10:07 PM, Ferenc Wagner wrote:
Daniel Lezcanodaniel.lezc...@free.fr writes:
On 06/09/2010 07:56 PM, Ferenc Wagner wrote:
here are basically the same patches, with some obvious errors corrected
and some unrelated documentation added. It actually survived some
On 07/15/2010 02:59 AM, Matt Helsley wrote:
On Fri, Jul 09, 2010 at 07:51:32PM -0700, Sukadev Bhattiprolu wrote:
From: Sukadev Bhattiprolusuka...@linux.vnet.ibm.com
Subject: [PATCH 1/2] Ensure frezer state has changed
A write to the freezer.state file does not gurantee that the state has
From: Ferenc Wagner wf...@niif.hu
Signed-off-by: Ferenc Wagner wf...@niif.hu
Signed-off-by: Daniel Lezcano dlezc...@fr.ibm.com
---
src/lxc/start.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/lxc/start.c b/src/lxc/start.c
index 92f44e3..1d4087c 100644
---
When lxc-init receives a SIGTERM, let's kill all the processes of
the pid namespace with kill -1. So the exit of the container will
happen gracefully with processes death cascade.
Signed-off-by: Daniel Lezcano dlezc...@fr.ibm.com
---
src/lxc/lxc_init.c | 14 --
1 files changed, 12
If lxc-init receives a SIGALRM, a timeout, it kills all the processes
of the container with SIGKILL. That will prevent the container to be
stuck when one process ignore the SIGTERM signal.
Each time a process exits, the timeout is resetted.
Signed-off-by: Daniel Lezcano dlezc...@fr.ibm.com
---
From: Ferenc Wagner wf...@niif.hu
Signed-off-by: Ferenc Wagner wf...@niif.hu
Signed-off-by: Daniel Lezcano dlezc...@fr.ibm.com
---
src/lxc/start.c | 22 ++
1 files changed, 14 insertions(+), 8 deletions(-)
diff --git a/src/lxc/start.c b/src/lxc/start.c
index
