Date: Fri, 31 Mar 2006 12:04:40 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: src-committers@freebsd.org, "Christian S.J. Peron" <csjp@freebsd.org>, cvs-all@freebsd.org, cvs-src@freebsd.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c Message-ID: <20060331100440.GA12785@garage.freebsd.pl> 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
--gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 31, 2006 at 09:06:32AM +0000, Robert Watson wrote: +>=20 +> On Fri, 31 Mar 2006, Peter Jeremy wrote: +>=20 +> >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 whe= n the +> >> filesystem is cleaned up, syslogd will automatically start logging ag= ain +> >> without requiring the reset. This makes syslogd(8) a bit more reliabl= e. +> > +> >My sole concern with this is that this means that syslogd will keep try= ing to write to the full filesystem - and the kernel will log the attempts = to write to a full=20 +> >filesystem. Whilst there's rate limiting in the kernel, this sort of f= eedback loop is undesirable. +>=20 +> 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=20 +> /var/tmp/vi.recover is also important. syslogd -l 90% could specify tha= t sylogd should not write log records, perhaps other than an "out of space = record" to a log file on=20 +> a file system with >=3D90% capacity. This prevents the kernel from spew= ing 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=3D0% and stop the rest at Avail=3D-4% maybe. Maybe we should take logs only from logpriv when Avail=3D0%... --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFELP64ForvXbEpPzQRAvsYAKC5vwyCufpIS1CTskib0yC7oISFxACeMxMZ 4X3bnAdEGZ56xWzdXpRUQ0U= =lHl/ -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060331100440.GA12785>