Date: Thu, 30 Mar 2006 13:42:16 -0800 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: "Christian S.J. Peron" <csjp@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c Message-ID: <20060330214216.GC86967@funkthat.com> In-Reply-To: <200603302104.k2UL4qF7086165@repoman.freebsd.org> References: <200603302104.k2UL4qF7086165@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian S.J. Peron wrote this message on Thu, Mar 30, 2006 at 21:04 +0000:
> csjp 2006-03-30 21:04:52 UTC
>
> FreeBSD src repository
>
> Modified files:
> usr.sbin/syslogd syslogd.c
> Log:
> Currently, if writing out a log entry fails, we unlink that log entry from our
> internal list of logfiles. So if writev(2) fails for potentially transient
> errors like ENOSPC, syslogd requires a restart, even if the filesystem has
> purged.
>
> 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.
I'd be cool if there was a log entry that logged the fact that we couldn't
write entries for a time due to no space on the device, so that going back
through the logs, you could understand why there was a big gap...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060330214216.GC86967>