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. To fix this syslogd2 needs to open each log file when it's started and keep it open. Apache's httpd does this with great success. A kill signal can be used per convention: "kill -1 `cat /var/run/syslogd.pid`" would flush the write buffer, close open logs, re-read the syslog.conf, and re-open the log files. This would also allow sysadmins to rotate logs per local requirements (age, size, diskfree, etc.). -- Roger Marquis Roble Systems Consulting http://www.roble.com/
