[OpenWrt-Devel] procd limits usage

Karl Palsson karlp at tweak.net.au
Wed Jan 7 09:44:25 EST 2015

Yousong Zhou <yszhou4tech at gmail.com> wrote:
> Okay.  But then I have no idea what's going wrong.  You can try adding
> getrlimit() call to hogger to see whether the soft/hard limit has
> indeed been imposed before exec() by procd.  BTW, the format of limits
> params allows setting both soft and hard limit for each resource type.
> As in the following
>                 procd_set_params limits "data=4000 8000"
> If only one value was given, only the soft limit is supposed to be
> changed with the hard limit left as it is.

Good to know, and I've tried it in that form now too.

> >
> > What does that actually limit?  Matching up names from the procd commit
> > RTLIMIT_xxx with "man ulimit" for instance isn't always obvious (to me
> > at least)
> My bad, should be RLIMIT_AS.

Ok, was looking in the right spaces now.  _any_ limit on AS stops my
process from starting (or, killing it immediately) I used up to as much
as     procd_append_param limits "as=512000 512000" with no help.

So, I guess that's "working"  I went back to RLIMIT_DATA, and added
getrlimit, and it indeed shows that procd is setting the limits, but it
still has no effect.  

Karl P

Sent using Mailpile, Free Software from www.mailpile.is
-------------- next part --------------
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list