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."
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
