Yousong Zhou 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 re
On 7 January 2015 at 20:16, Karl Palsson wrote:
>
> Yousong Zhou wrote:
>>
>> Which libc was in use? Because RLIMIT_DATA only applies to those
>> allocated by brk() and sbrk(), while malloc() of glibc may fallback to
>> mmap() if sbrk() fails. AFAIK, malloc() of uClibc for MIPS in OpenWrt
>> ut
Yousong Zhou wrote:
>
> Which libc was in use? Because RLIMIT_DATA only applies to those
> allocated by brk() and sbrk(), while malloc() of glibc may fallback to
> mmap() if sbrk() fails. AFAIK, malloc() of uClibc for MIPS in OpenWrt
> utilizes only sbrk() with the default config.
whatever th
On 7 January 2015 at 00:19, Karl Palsson wrote:
> Hi,
>
> I'm trying out using procd to kill/restart processes that use too much
> memory, using the "limits" feature added in
> https://lists.openwrt.org/pipermail/openwrt-devel/2013-December/022793.html
> and I've confirmed that it's available in t
Hi,
I'm trying out using procd to kill/restart processes that use too much
memory, using the "limits" feature added in
https://lists.openwrt.org/pipermail/openwrt-devel/2013-December/022793.html
and I've confirmed that it's available in the BB branch procd that I'm
testing against.
My init script
