From owner-cvs-src@FreeBSD.ORG Sat Feb 26 02:42:30 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9571216A4CE; Sat, 26 Feb 2005 02:42:30 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B34E43D5D; Sat, 26 Feb 2005 02:42:30 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 39BFE72DD4; Fri, 25 Feb 2005 18:42:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 3413972DCB; Fri, 25 Feb 2005 18:42:30 -0800 (PST) Date: Fri, 25 Feb 2005 18:42:30 -0800 (PST) From: Doug White To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: <863bvnl6fp.fsf@xps.des.no> Message-ID: <20050225184131.Q32072@carver.gumbysoft.com> References: <200502220803.j1M839fn013604@repoman.freebsd.org> <20050222082558.GB10624@cell.sick.ru> <20050223134627.GA21396@cell.sick.ru> <863bvnl6fp.fsf@xps.des.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE cc: cvs-src@freebsd.org cc: Mike Silbersack cc: Gleb Smirnoff cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/etc syslog.conf X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 02:42:30 -0000 On Wed, 23 Feb 2005, [iso-8859-1] Dag-Erling Sm=F8rgrav wrote: > Gleb Smirnoff writes: > > Yes, a good plan. btw, syslogd does some ratelimiting itself. However, = when > > system is low on kernel memory, new valid ARP entries fail to install > > with _two_ debug messages. Since two different messages are printed one > > after other, syslogd's limiting does not work. Example: > > > > Feb 2 09:00:01 gw-core1 /kernel: arplookup 217.72.145.208= failed: > > could not allocate llinfo > > Feb 2 09:00:01 gw-core1 /kernel: arpresolve: can't alloca= te llinfo > > for 217.72.145.208rt > > The second message can simply be removed, since (from my quick reading > of the code) it can only occur if the first has already occurred. Are you sure? The second was the telltale that you have broken Linux boxes on your network. :-) --=20 Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org