Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-08-15 Thread Rafael Aquini
On Tue, Aug 12, 2014 at 09:29:17AM +0200, Manfred Spraul wrote: > Right now, each new IPC namespace starts with the kernel default values. > This means that changes that were made to the limits get overwritten. > > With this patch, a new namespace inherits the settings from the parent >

Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-08-15 Thread Rafael Aquini
On Tue, Aug 12, 2014 at 09:29:17AM +0200, Manfred Spraul wrote: Right now, each new IPC namespace starts with the kernel default values. This means that changes that were made to the limits get overwritten. With this patch, a new namespace inherits the settings from the parent namespace,

Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-08-12 Thread Manfred Spraul
Hi Eric, On 08/12/2014 12:37 PM, Eric W. Biederman wrote: Manfred Spraul writes: Sigh. Patches for new code during the merge window. It is a really rotten time to look at new things. Right now, each new IPC namespace starts with the kernel default values. This means that changes that were

Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-08-12 Thread Eric W. Biederman
Manfred Spraul writes: Sigh. Patches for new code during the merge window. It is a really rotten time to look at new things. > Right now, each new IPC namespace starts with the kernel default values. > This means that changes that were made to the limits get overwritten. > > With this patch, a

[PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-08-12 Thread Manfred Spraul
Right now, each new IPC namespace starts with the kernel default values. This means that changes that were made to the limits get overwritten. With this patch, a new namespace inherits the settings from the parent namespace, which is less surprising. The patch updates - SysV msg - SysV sem -

[PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-08-12 Thread Manfred Spraul
Right now, each new IPC namespace starts with the kernel default values. This means that changes that were made to the limits get overwritten. With this patch, a new namespace inherits the settings from the parent namespace, which is less surprising. The patch updates - SysV msg - SysV sem -

Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-08-12 Thread Eric W. Biederman
Manfred Spraul manf...@colorfullife.com writes: Sigh. Patches for new code during the merge window. It is a really rotten time to look at new things. Right now, each new IPC namespace starts with the kernel default values. This means that changes that were made to the limits get overwritten.

Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-08-12 Thread Manfred Spraul
Hi Eric, On 08/12/2014 12:37 PM, Eric W. Biederman wrote: Manfred Spraul manf...@colorfullife.com writes: Sigh. Patches for new code during the merge window. It is a really rotten time to look at new things. Right now, each new IPC namespace starts with the kernel default values. This means

Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-06-06 Thread Serge E. Hallyn
Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com): > [CC += Eric and containers@] > > Hi Manfred, > > On Thu, May 29, 2014 at 8:46 PM, Manfred Spraul > wrote: > > Right now, each IPC namespace starts with the kernel boot standard > > settings. > > This patch changes that: > > Now

Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-06-06 Thread Serge E. Hallyn
Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com): [CC += Eric and containers@] Hi Manfred, On Thu, May 29, 2014 at 8:46 PM, Manfred Spraul manf...@colorfullife.com wrote: Right now, each IPC namespace starts with the kernel boot standard settings. This patch changes that:

Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-06-05 Thread Michael Kerrisk (man-pages)
[CC += Eric and containers@] Hi Manfred, On Thu, May 29, 2014 at 8:46 PM, Manfred Spraul wrote: > Right now, each IPC namespace starts with the kernel boot standard > settings. > This patch changes that: > Now each new namespace starts with the settings from the parent > namespace. > > The

Re: [PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-06-05 Thread Michael Kerrisk (man-pages)
[CC += Eric and containers@] Hi Manfred, On Thu, May 29, 2014 at 8:46 PM, Manfred Spraul manf...@colorfullife.com wrote: Right now, each IPC namespace starts with the kernel boot standard settings. This patch changes that: Now each new namespace starts with the settings from the parent

[PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-05-29 Thread Manfred Spraul
Right now, each IPC namespace starts with the kernel boot standard settings. This patch changes that: Now each new namespace starts with the settings from the parent namespace. The patch updates - SysV msg - SysV sem - SysV shm - POSIX mqueues It's just a proposal - only partially tested --

[PATCH 3/3] ipc namespace: copy settings from parent namespace

2014-05-29 Thread Manfred Spraul
Right now, each IPC namespace starts with the kernel boot standard settings. This patch changes that: Now each new namespace starts with the settings from the parent namespace. The patch updates - SysV msg - SysV sem - SysV shm - POSIX mqueues It's just a proposal - only partially tested --