On Thu, 17 Jun 1999, Eric Dahnke wrote: > We're having a problem with a mailserver. The machine does about 11,000 > msgs a day. At heaviest times smtp concurrency goes up to 60/150 or > 70/150. During these times load avg goes up to 20, and syslog is eating > %70 of CPU. At that point the messages and maillog files are at say 20M > each. If we dev/null the logs, load returns to 1 2 or 3 load avg. If you use tcpserver I suggest you to use cyclog instead. By the way your problem is syslog's writing method. Linux's syslog does a sync after each line it writes. If you put a dash (-) before the mail log file (eg. /var/log/maillog), it won't sync. This isn't a perfect solution but it works if your system doesn't crash every week. -- Regards: Kevin (Balazs)
