Date: Thu, 22 Jan 2004 14:50:18 -0800 (PST) From: Kris Kennaway <kris@obsecurity.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/61664: syslogd speedup Message-ID: <200401222250.i0MMoI2U047404@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/61664; it has been noted by GNATS. From: Kris Kennaway <kris@obsecurity.org> To: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: bin/61664: syslogd speedup Date: Thu, 22 Jan 2004 14:44:14 -0800 On Wed, Jan 21, 2004 at 10:15:22AM +0100, Divacky Roman wrote: > >Description: > When syslogd logs kernel messages it does it quite weird way. It reads > buffer from /dev/kmsg and then writes it into log file fsync()ing after > EACH newline.. this is very slow and much less secure than fsync()ing > it after whole buffer... this patch implements such behviour Why do you say "much less secure"? It's possible the fsync() behaviour is deliberate - this may allow kernel messages to be written to disk if a panic occurs before the entire buffer is filled, which is useful for analysis of the crash. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200401222250.i0MMoI2U047404>