SUMMARY: Recommended /etc/system values for busy webserver?

From: David Lowenstein <>
Date: Tue Aug 13 2002 - 11:44:39 EDT
Thanks to 

Yura Pismerov 
Andrew J Caines

and a few more people whose emails I probably deleted. 

The consensus seemed to be to remove the values from /etc/system that I
migrated over from a similar server, and then to just go into production
with the defaults, with the exception of 

set noexec_user_stack = 1
set noexec_user_stack_log = 1

for security purposes, and

set hme:hme_adv_autoneg_cap=0
set hme:hme_adv_100T4_cap=0 
set hme:hme_adv_100fdx_cap=1 
set hme:hme_adv_100hdx_cap=0 
set hme:hme_adv_10fdx_cap=0 
set hme:hme_adv_10hdx_cap=0

to force 100 mbit full duplex ethernet

On Andrew Caines' suggestion I've installed orca to collect performance
data so I can make an intelligent decision if I see a performance problem,
instead of blindly changing /etc/system values because the "kernel tuning
folklore" says so. Adrian Cockroft says about the same thing in his
performance tuning book, don't believe in /etc/system folklore. It's not
to say that you can't reap performance gains from kernel tuning, you
should just have a good documented reason why you make each change.

Dave Lowenstein
Instructional Technology Services
San Diego State University
sunmanagers mailing list
Received on Tue Aug 13 11:47:21 2002

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:52 EST