Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]) on Fri, Oct 22, 1999 at 05:37:22PM -0400:
> >>>>> "Andreas" == Andreas Siegert <[EMAIL PROTECTED]> writes:
>
> Andreas> Quoting Roger Marquis ([EMAIL PROTECTED]) on Wed, Oct 20, 1999 at
>09:49:00AM -0700:
> >> Bennett Todd <[EMAIL PROTECTED]> wrote:
> >> >While the focus of this design effort is on security, my biggest concern
> >> >is performance --- and it bears on security.
> >>
> >> The biggest performance problem is writing logfiles. Syslogd opens the
> >> file for each message and then closes it after writing. This causes
> >> serious i/o problems, especially when the files grow quickly or larger
> >> than 1 or 2 MB.
>
> Andreas> I strongly suggest a config option that will allow syslog to write to disc
> Andreas> with syncing to not loose any critical data.
>
> Ummm... is there _really_ a syslogd hat is so stupid as to open/close the
> file every time? Wow...
>
> man fsync
>
> I agree that calling fsync() after each write() should be _optional_ (I
> currently LD_PRELOAD a null fsync() in order to get syslogd to do something
> other that sit in the kernel in IOWAIT).
I have not seen a syslog doing an open on every record, but the regular syslog
on Linux does an fsync way to often. Fortunately that can be turned off per
log stream.
afx
--
SuSE Muenchen GmbH Phone: +49-89-42769-0
Stahlgruberring 28 Fax: +49-89-42017701
D-81829 Muenchen, Germany
May the Source be with you!
