From owner-cvs-src@FreeBSD.ORG Fri Mar 31 10:32:14 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 4475816A427; Fri, 31 Mar 2006 10:32:14 +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 C7CA143D62; Fri, 31 Mar 2006 10:32:13 +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 6623146C00; Fri, 31 Mar 2006 05:32:13 -0500 (EST) Date: Fri, 31 Mar 2006 10:32:13 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Pawel Jakub Dawidek In-Reply-To: <20060331100440.GA12785@garage.freebsd.pl> Message-ID: <20060331103033.F88223@fledge.watson.org> References: <200603302104.k2UL4qF7086165@repoman.freebsd.org> <20060331080654.GB776@turion.vk2pj.dyndns.org> <20060331090421.I9972@fledge.watson.org> <20060331100440.GA12785@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Peter Jeremy , src-committers@freebsd.org, "Christian S.J. Peron" , 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 10:32:14 -0000 On Fri, 31 Mar 2006, Pawel Jakub Dawidek wrote: > +> 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. > > One of the things I like about UFS is that it has 8% of reserved space and > when syslogd is running as root, it can still log, even when /var/ is full > of users' data. Of course there should be separate /var/log/ partition, > but... > > In my opinion it'll be good, if we can stop logging various levels when we > hit Avail=0% and stop the rest at Avail=-4% maybe. Maybe we should take logs > only from logpriv when Avail=0%... The trick will be balancing flexibility with complexity for the administrator. -s foopercent is easy for an administrator to understand, and conditional logging of message types based on percentage is not. I can imagine a useful middle ground on the order of -s info,80 or such, which means don't log info and lower when about 80%, but we'd need to think a little carefully about how to present this sort of thing so it's useful as opposed to simply confusing. :-) Robert N M Watson