RT-N10: OOM on large syslog

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install bittorrent, enter "1000" or more in "limit concurrent connections" 
option, forward ports for it. Limit misc_conntrack_x=1024 (or even 512 in new 
firmware)
2. Start to seed any popular file
3. In system log there will be contionous "conntrack table full, dropping 
packet"
4. system log wil consume about 300K of ram, and OOM killer is called after 3 
hours/1 week regarding of activity, killing, at least, dnsmasq

What is the expected output? What do you see instead?
expected: router does not hand with OOM, rotating log, and operationg normally
got: it does not

What version of the product are you using?
problem is here since 2308

Please provide any additional information below.
RT-N10 has got a small amount of memory, and log size 150K*2 is really bad idea 
here.
Tuneable log size from http, or autoselecting log size depending of total 
memory size is good idea, 2*16K will be just fine for this router.

Original issue reported on code.google.com by d77...@mail.ru on 21 Apr 2011 at 4:16

[GoogleCodeExporter]

thank you, will look into the issue

Original comment by themiron.ru on 21 Apr 2011 at 8:35

[GoogleCodeExporter]

Here is my suggestion:

1) /dev - max. size 100K for all devices

2) /tmp - 1/4 RAM for 16Mb models, 1/2 RAM for all others

3) syslogd - 2x32K for 16Mb models, 2x200K for all others

Original comment by lly.dev on 30 Sep 2011 at 9:24

• Changed title: RT-N10: OOM on large syslog

[GoogleCodeExporter]

anp/hsw, 30.09.2011 15:48:31:
/dev - ok
/tmp - i think there is must be configurable option in web-interfeace, tmpfs 
size can be changed via mount /tmp -o remount,size=xxx in any moment. 1/4RAM 
should be ok in most cases.
syslogd - yes, 2x32 will be fine, optimal size is "kernel start log size"+10K

Original comment by themiron.ru on 30 Sep 2011 at 10:17

[GoogleCodeExporter]

Fixed in r3353

Original comment by lly.dev on 30 Sep 2011 at 2:26

• Changed state: Fixed