Re: [squid-users] Re: cant increase max files open in "limits.conf"

Actually, you are specifying the directive below the # End of file, so
it doesn't get applied.
Move that line to the end.

Also, i don't believe those lines inside the debian script takes
effect, as it is run by root, and you probably run squid as a
different user. The right thing to do is to edit the limits.conf
properly.

On Sun, May 12, 2013 at 5:38 AM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
> On 12/05/2013 7:50 p.m., Ahmad wrote:
>>
>> hi Amos ,
>> thanks alot for reply ,
>> i viewed
>>
>> root_at_debian:~# nano /etc/init.d/squid3
>> =============================
>> i found that ulimit was set to 65535
>> ===================================
>> root_at_debian:~# cat /etc/init.d/squid3 | grep ulimit
>> ulimit -n 65535
>> ulimit -n 65535
>> ===========================================================
>>
>> does that mean that this value is overwriting the value when i type
>> ulimit -n from bash shell ???
>
>
> Yes it does.
>
>
>>
>> i also wan tto ask if this issue has relation to rate limit kernel
>> i noted some logs in
>> /var/log/messages
>> root_at_vyatta:~# tailf /var/log/messages
>> May 11 17:32:29 vyatta kernel: [243759.737860] net_ratelimit: 1 callbacks
>> suppressed
>> May 11 17:32:36 vyatta kernel: [243766.446286] net_ratelimit: 11 callbacks
>> suppressed
>> May 11 17:32:47 vyatta kernel: [243777.487244] net_ratelimit: 8 callbacks
>> suppressed
>> May 11 17:33:01 vyatta kernel: [243791.353330] net_ratelimit: 3 callbacks
>> suppressed
>
>
> No idea. I've never seen those kernel mesages before.
>
> Amos
Received on Sun May 12 2013 - 11:52:20 MDT