From owner-freebsd-current@FreeBSD.ORG Tue May 12 13:23:43 2009 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 BEA80106566C for ; Tue, 12 May 2009 13:23:43 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 69DB78FC13 for ; Tue, 12 May 2009 13:23:43 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 22BBD19E045; Tue, 12 May 2009 15:23:41 +0200 (CEST) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8956919E043; Tue, 12 May 2009 15:23:35 +0200 (CEST) Message-ID: <4A097857.5040007@quip.cz> Date: Tue, 12 May 2009 15:23:35 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: Dmitry Morozovsky References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, gad@FreeBSD.org Subject: Re: newsyslog(8) patch for both size and time checks 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: Tue, 12 May 2009 13:23:44 -0000 Dmitry Morozovsky wrote: > Dear colleagues, > > for now, if log is configured to be rotated in time manner, its size is not > checked, so /var/log may be DoSed by some service (in our case, it was mad DHCP > client which fills up our /var/log with dhcpd log; our newsyslog.conf line was > > /var/log/dhcpd 640 5 5000 @T00 JC > > The following simple patch should fix the problem. Any objection to commit > this? I can't judged the patch, but I am +1 for this functionality. Miroslav Lachman