From owner-freebsd-current@FreeBSD.ORG Sat Aug 16 01:23:23 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58CAD106564A for ; Sat, 16 Aug 2008 01:23:23 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outL.internet-mail-service.net (outl.internet-mail-service.net [216.240.47.235]) by mx1.freebsd.org (Postfix) with ESMTP id 5AA618FC19 for ; Sat, 16 Aug 2008 01:23:23 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 5DF5221F0; Fri, 15 Aug 2008 18:23:23 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 7670A2D60CE; Fri, 15 Aug 2008 18:23:22 -0700 (PDT) Message-ID: <48A62C09.4090004@elischer.org> Date: Fri, 15 Aug 2008 18:23:21 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Erol Akarsu References: <136625.5517.qm@web45211.mail.sp1.yahoo.com> In-Reply-To: <136625.5517.qm@web45211.mail.sp1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, cpghost Subject: Re: Limiting icmp unreach response fron 348 to 200 packets/sec X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Aug 2008 01:23:23 -0000 Erol Akarsu wrote: > Hi, > > Thanks for helping this. > > Now, I am getting "Limiting icmp unreach response fron 348 to 200 packets/sec" > > In which conditions can we get this? does this effect functionality of the system? > How can I solve this issue? > It means something in your network is not working well and the system is being tempted to send lots of ICMP packets in complaint, but it is only sending200 complaints per second because it has been told to limit itself to that number. Using tcpdump to see what ICMP packets ARE being sent would be a good place ot start. Also FreeBSD has a good set of man pages unlike many Linux distributions. So try the man pages and google when you hit a problem.. e.g. man -k icmp will give you a list of man pages that hace something to do with icmp man -k sysctl man 1 intro man 2 intro man 3 intro man 4 intro man 9 intro are also good starting places. man man is worth a look too. > Thanks > > Erol Akarsu > > > > > ----- Original Message ---- > From: cpghost > To: Erol Akarsu > Cc: freebsd-current@freebsd.org > Sent: Friday, August 15, 2008 7:42:05 PM > Subject: Re: Freeswitch on latest FBSD > > On Fri, Aug 15, 2008 at 04:23:39PM -0700, Erol Akarsu wrote: >> Can you help me on setting other limits? I did the following but it >> did not change. I would like this like I do in linux: >> >> ulimit -c unlimited >> >> Could you please tell me how I will do it on FreeBSD? > > Which shell are your using? > > With csh/tcsh: > > # limit > cputime unlimited > filesize unlimited > datasize 524288 kbytes > stacksize 65536 kbytes > coredumpsize unlimited > memoryuse unlimited > vmemoryuse unlimited > descriptors 7092 > memorylocked unlimited > maxproc 3546 > sbsize unlimited > > # limit stacksize > stacksize 65536 kbytes > > # limit stacksize 32000 > # limit stacksize > stacksize 32000 kbytes > > # limit stacksize unlimited > # limit stacksize > stacksize 65536 kbytes > > With /bin/sh: > > # ulimit -a > cpu time (seconds, -t) unlimited > file size (512-blocks, -f) unlimited > data seg size (kbytes, -d) 524288 > stack size (kbytes, -s) 65536 > core file size (512-blocks, -c) unlimited > max memory size (kbytes, -m) unlimited > locked memory (kbytes, -l) unlimited > max user processes (-u) 3546 > open files (-n) 7092 > virtual mem size (kbytes, -v) unlimited > sbsize (bytes, -b) unlimited > > # ulimit -s 32200 > # ulimit -s > 32200 > > # ulimit -s unlimited > # ulimit -s > 65536 > > If you need to rise other limits (say, open files, etc...), you'll > need to crank up the sysctl value. You can get a list of all sysctl > values like this: > > # sysctl -a | more > >> Thanks > > -cpghost. >