Quoting j...@linux.vnet.ibm.com (j...@linux.vnet.ibm.com):
> From: Jian Xiao
>
> Signed-off-by: Jian Xiao
Two issues below.
> ---
> src/lxc/conf.c| 123
> +
> src/lxc/conf.h|2 +
> src/lxc/confile.c | 32 ++
> 3 f
Quoting J. Xiao (j...@linux.vnet.ibm.com):
> I checked all the capabilities are up before opening shmmax file.
> If I seteuid to 0, the open succeeds. There seems to be a difference
> between having a root euid and a regular user having root capabilities
> in terms of writing to shmmax file.
Yup
From: Jian Xiao
Signed-off-by: Jian Xiao
---
src/lxc/conf.c| 123 +
src/lxc/conf.h|2 +
src/lxc/confile.c | 32 ++
3 files changed, 157 insertions(+), 0 deletions(-)
diff --git a/src/lxc/conf.c b/src/lxc/conf.c
inde
From: Jian Xiao
Often system admin needs to change /proc/sys/kernel/shmmax and shmall values
to run a job. These values are not inherited by container and needs to be
passed to container when starting the job.
This patch adds "lxc.shmmax" and "lxc.shmall" configuration variable
for lxc-execute "
I checked all the capabilities are up before opening shmmax file.
If I seteuid to 0, the open succeeds. There seems to be a difference
between having a root euid and a regular user having root capabilities
in terms of writing to shmmax file.
On 7/5/2012 4:49 PM, Stéphane Graber wrote:
> On 07/05
