Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Technical issues on Linux



   From: Rich Braun <richb at pioneer.ci.net>

   If syslogd's log files get bigger than a few megabytes, the
   overhead of this fsync() on a busy system causes major CPU
   thrashing.

Though it seems to this naive person that the overhead of the fsync
should be limited to the number of disk blocks that have been modified
by syslogd since the last time it did an fsync.  Is the kernel keeping
the data structures to allow fsync to be implemented efficiently?

Dale




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org