Quoting Bostjan Skufca (bost...@a2o.si):
> On 15 September 2015 at 19:46, Serge Hallyn wrote:
> > It sounds like it may be worthwhile. The patch shouldn't be huge, so
> > I think it's worth creating the patch and sending it to the list. Do
> > make sure to give a detailed description of how you'
On 15 September 2015 at 19:46, Serge Hallyn wrote:
> It sounds like it may be worthwhile. The patch shouldn't be huge, so
> I think it's worth creating the patch and sending it to the list. Do
> make sure to give a detailed description of how you'll use it. (Don't
> assume I'll remember :)
Tnx
It sounds like it may be worthwhile. The patch shouldn't be huge, so
I think it's worth creating the patch and sending it to the list. Do
make sure to give a detailed description of how you'll use it. (Don't
assume I'll remember :)
thanks,
-serge
Quoting Bostjan Skufca (bost...@a2o.si):
> Open
Open files limit is the one I need (for unpriv. containers), but if
framework is set correctly, others can be added too.
Open files limit can not be raised later on when container switches
into unprivileged mode, so I need to set it before that, but not in
external process. Setting this in process
Which limits would you be intending to set?
Quoting Bostjan Skufca (bost...@a2o.si):
> (there was no response on this subject)
>
> I checked the documentation, there is nothing on this subject.
>
> Serge, Stephane:
> I am considering implementing lxc.ulimit.XXX = X feature. Would that
> be somet
(there was no response on this subject)
I checked the documentation, there is nothing on this subject.
Serge, Stephane:
I am considering implementing lxc.ulimit.XXX = X feature. Would that
be something that is interesting for inclusion in main LXC releases
(1.1.x)?
b.
On 18 August 2015 at 11
Hi all,
is there any elegant way for setting unpriv. container ulimits, other
than setting it in current shell and starting container from that
shell (and scripting all this together)?
Hooks do not work, as they are executed as subprocesses.
b.
___
lxc
