From owner-cvs-src@FreeBSD.ORG Fri Mar 31 16:51:27 2006 Return-Path: X-Original-To: cvs-src@freebsd.org 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 29F6A16A426 for ; Fri, 31 Mar 2006 16:51:27 +0000 (UTC) (envelope-from csjp@FreeBSD.org) Received: from ems01.seccuris.com (ems01.seccuris.com [204.112.0.35]) by mx1.FreeBSD.org (Postfix) with SMTP id AFAB943D55 for ; Fri, 31 Mar 2006 16:51:25 +0000 (GMT) (envelope-from csjp@FreeBSD.org) Received: (qmail 9548 invoked by uid 86); 31 Mar 2006 17:00:08 -0000 Received: from unknown (HELO ?192.168.11.101?) (192.168.11.101) by ems01.seccuris.com with SMTP; 31 Mar 2006 17:00:08 -0000 Message-ID: <442D5E23.7010208@FreeBSD.org> Date: Fri, 31 Mar 2006 10:51:47 -0600 From: "Christian S.J. Peron" User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <200603302104.k2UL4qF7086165@repoman.freebsd.org> <20060331080654.GB776@turion.vk2pj.dyndns.org> <20060331090421.I9972@fledge.watson.org> <442D475C.2030604@FreeBSD.org> <20060331163221.Q88223@fledge.watson.org> In-Reply-To: <20060331163221.Q88223@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Jeremy , src-committers@freebsd.org, cvs-all@freebsd.org, cvs-src@freebsd.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 31 Mar 2006 16:51:27 -0000 Robert Watson wrote: > > On Fri, 31 Mar 2006, Christian S.J. Peron wrote: > >> Although I agree this is a good idea, I think it would be more >> appropriate to place these kinds of checks in newsyslog(8) so that >> other programs logging can take advantage of this. > > > The program generating the log message is presumably the one that has > to decide not to generate it if space is low. Log messages currently > come from syslogd. Are you actually suggesting that syslogd should > read the newsylogd.conf file to find settings? > > Robert N M Watson > > > No not necessarily, Just that perhaps we should add a "This log file can only consume %X of the file system is resides on" and rotate the files possibly? I have not given it a great deal of thought as of yet. In any case, I am open to suggestions for this problem. I agree the feedback loop is not desirable. I do know however that issues like mail spools temporarily filling up the file systems resulting in syslogd stop working is problematic. -- Christian S.J. Peron csjp@FreeBSD.ORG FreeBSD Committer FreeBSD Security Team