From owner-cvs-src@FreeBSD.ORG Fri Mar 31 09:06:41 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 5B96D16A400; Fri, 31 Mar 2006 09:06:41 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD13343D68; Fri, 31 Mar 2006 09:06:36 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id A7E5246BE0; Fri, 31 Mar 2006 04:06:35 -0500 (EST) Date: Fri, 31 Mar 2006 09:06:32 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Jeremy In-Reply-To: <20060331080654.GB776@turion.vk2pj.dyndns.org> Message-ID: <20060331090421.I9972@fledge.watson.org> References: <200603302104.k2UL4qF7086165@repoman.freebsd.org> <20060331080654.GB776@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@freebsd.org, src-committers@freebsd.org, "Christian S.J. Peron" , cvs-all@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 09:06:41 -0000 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. Robert N M Watson