On Sat, 21 Aug 2004 17:49, Iago Rubio <iago.rubio@xxxxxxxxxxxxx> wrote: > ITOH it's buffered architecture make it really bad for developers or > kernel debuggers as log messages does not arise instantly, but when the > buffer is big enought to write it out (the buffering can be disabled). How is this different from the regular syslogd? I have configured lots of machines with the "-" option on all log files to use buffering and reduce IO load. I haven't found any great problems with that, often a kernel bug will break even non-buffered disk IO... -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
