1. What is "asynchronous logging" as mentioned for syslog.conf?
It seems that syslog wants to log synchronously by default - it may not have much effect in some environments, but if you have a lot of things going on that get logged, it can hog a lot of time constantly writing the the disk. In our mail server environment, setting logging to asynchronous reduced the load average by a 1or so during peak loads.
You can prepend the logfile names with "-" to make them synchronous, once syslogd is restarted.
Err... still confused as to _what_is_ synchronous vs. asynchronous logging. Can I buy a Clue, here?
2. What the heck are those tcp_* settings in sysctl.conf?
They just turn off some of the tcp/ip bells and whistles, and/or put reasonable limits on some things - and I've not seen a downside in daily use. You'll notice that the big boys do things like that when they are tuning systems to run network benchmarks...
Any FM I can R about this? I'd like to learn some more.
-- Rodolfo J. Paiz rpaiz@xxxxxxxxxxxxxx
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
