Date: Fri, 25 Feb 2005 18:42:30 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/etc syslog.conf Message-ID: <20050225184131.Q32072@carver.gumbysoft.com> In-Reply-To: <863bvnl6fp.fsf@xps.des.no> References: <200502220803.j1M839fn013604@repoman.freebsd.org> <20050222082558.GB10624@cell.sick.ru> <20050223134627.GA21396@cell.sick.ru> <863bvnl6fp.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Feb 2005, [iso-8859-1] Dag-Erling Sm=F8rgrav wrote: > Gleb Smirnoff <glebius@freebsd.org> 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 <kern.debug> gw-core1 /kernel: arplookup 217.72.145.208= failed: > > could not allocate llinfo > > Feb 2 09:00:01 <kern.debug> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050225184131.Q32072>