Date: Fri, 31 Mar 2006 09:14:36 -0600 From: "Christian S.J. Peron" <csjp@FreeBSD.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: Peter Jeremy <peterjeremy@optushome.com.au>, src-committers@freebsd.org, cvs-all@freebsd.org, cvs-src@freebsd.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c Message-ID: <442D475C.2030604@FreeBSD.org> In-Reply-To: <20060331090421.I9972@fledge.watson.org> References: <200603302104.k2UL4qF7086165@repoman.freebsd.org> <20060331080654.GB776@turion.vk2pj.dyndns.org> <20060331090421.I9972@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > > Robert N M Watson > > 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. -- Christian S.J. Peron csjp@FreeBSD.ORG FreeBSD Committer FreeBSD Security Team
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?442D475C.2030604>