> I don't understand why remote logging would slow down an application. > That is likely due to my ignorance. I thought that the app used the > syslog() calls to send the information to the resident syslogd. The > resident syslogd would then "do whatever". Is syslogd single threaded > that it would be negatively impacted by a high rate of > logging? Are the > syslog() calls synchronous? I guess I could read the code, but I don't > have the time right now.
No, but they can be overrun. Like I said, you have to be doing a LOT of logging to hit the limit, but there is one. We hit it in a high-performance mail server -- if you're handling a more than 10-12 msg/sec range, syslog can get behind, and it doesn't handle that well. The app then slows down as it has to format the message and then log it. You probably won't hit the limit with a few machines, but if you're concentrating a lot of machines to a single syslog, you might hit it. Thus the warning. -- db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
