From owner-cvs-src@FreeBSD.ORG Wed Apr 12 04:58:02 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 3ACB716A400 for ; Wed, 12 Apr 2006 04:58:02 +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 52AC743D69 for ; Wed, 12 Apr 2006 04:57:57 +0000 (GMT) (envelope-from csjp@FreeBSD.org) Received: (qmail 24037 invoked by uid 86); 12 Apr 2006 05:12:03 -0000 Received: from unknown (HELO ?127.0.0.1?) (204.112.0.37) by ems01.seccuris.com with SMTP; 12 Apr 2006 05:12:03 -0000 Message-ID: <443C88DA.5000309@FreeBSD.org> Date: Tue, 11 Apr 2006 23:58:02 -0500 From: "Christian S.J. Peron" User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Brooks Davis References: <200603302104.k2UL4qF7086165@repoman.freebsd.org> <20060331080654.GB776@turion.vk2pj.dyndns.org> <20060331090421.I9972@fledge.watson.org> <20060411184559.GA14844@odin.ac.hmc.edu> In-Reply-To: <20060411184559.GA14844@odin.ac.hmc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Jeremy , src-committers@FreeBSD.org, Robert Watson , 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: Wed, 12 Apr 2006 04:58:02 -0000 Brooks Davis wrote: > On Fri, Mar 31, 2006 at 09:06:32AM +0000, Robert Watson wrote: > >> On Fri, 31 Mar 2006, Peter Jeremy wrote: >> >> >>> On Thu, 2006-Mar-30 21:04:52 +0000, Christian S.J. Peron wrote: >>> >>>> This change allows syslogd to ignore ENOSPC space errors, so that when >>>> the >>>> filesystem is cleaned up, syslogd will automatically start logging again >>>> without requiring the reset. This makes syslogd(8) a bit more reliable. >>>> >>> My sole concern with this is that this means that syslogd will keep trying >>> to write to the full filesystem - and the kernel will log the attempts to >>> write to a full filesystem. Whilst there's rate limiting in the kernel, >>> this sort of feedback loop is undesirable. >>> >> What I'd like to see is an argument to syslogd to specify a maximum full >> level for the target file system. Log data is valuable, but being able to >> write to /var/tmp/vi.recover is also important. syslogd -l 90% could >> specify that sylogd should not write log records, perhaps other than an >> "out of space record" to a log file on a file system with >=90% capacity. >> This prevents the kernel from spewing about being out of space also. The >> accounting code does exactly this, for identical reasons. >> > > Anyone working on an implementation of this? I just had more machines > blow up due to out of control logs from a crashing process in an > infinite coredump loop so I'll take a shot at it if someone else isn't. > > IMO, what's really important is to keep enough space that newsyslog can > do it's job. I have plenty of log file that should compress at better > than 10:1 since they are all the same two lines over and over, but it > doesn't do any good when newsyslog can't compress the file and create a > new one. > > -- Brooks > > Yes, I am still interested in solving this problem. I am on the west coast for a couple more days. If it's causing problems, you can go ahead and back it out until we can figure out a better solution. Cheers -- Christian S.J. Peron csjp@FreeBSD.ORG FreeBSD Committer FreeBSD Security Team