spiceiorew.blogg.se

This too is an important tuning parameter regarding the performance of the Apache web server. The option MaxClients specifies the number of simultaneous requests that can be supported by Apache. Load operation, a value of 16 is recommended by various benchmarks on the Internet. This is, again, an important tuning parameter regarding the performance of the Apache web server. The option StartServers specifies the number of child server processes that will be created by Apache on start-up. For high load operation, a value of 64 is recommended by various benchmarks on the Internet. This is also an important tuning parameter regarding the performance of the Apache web

The option MaxSpareServers specifies the maximum number of idle child server processes for Apache, which is not handling a request. High load operation, a value of 16 is recommended by various benchmarks on the Internet. This is an important tuning parameter regarding the performance of the Apache web server. The option MinSpareServers specifies the minimum number of idle child server processes for Apache, which is not handling a request. The value of 15 seconds is a good average for server performance. The option KeepAliveTimeout specifies how much time, in seconds, Apache will wait for a subsequent request before closing the connection. For server performance, it's recommended to allow unlimited requests. When the value of this option is set to 0 then unlimited The option MaxKeepAliveRequests specifies the number of requests allowed per connection when the KeepAlive option above is set to On. For better performance, it's recommended to set this option to On, and allow more than one request per connection. The option KeepAlive, if set to On, specifies enabling persistent connections on this web server. You can safely leave this option on its default values. The option Timeout specifies the amount of time Apache will wait for a GET, POST, PUT request and ACKs on transmissions. When you set the location to /dev/null,Īpache allows you to include the content of this file in nf file, and in this manner, you have just one file that handles all your configuration parameters for simplicity. The option AccessConfig specifies the location of the old nf file that Apache read after it finished reading the srm.conf file.

To /dev/null, Apache allows you to include the content of this file in nf file, and in this manner, you have just one file that handles all your configuration The option ResourceConfig specifies the location of the old srm.conf file that Apache read after it finished reading the nf file. This option is only required when you configure Apache in standalone mode. The option PidFile specifies the location where the server will record the process id of the daemon when it starts. It allows Apache to know where it can find its configuration files when it starts. The option ServerRoot specifies the directory in which the configuration files of the Apache server lives. It's highly recommended to run Apache in standalone type for You can run it from the super-server inetd, or as standalone daemon. The option ServerType specifies how Apache should run on the system. This tells nf file to set itself up for this particular configuration setup with: ServerAdmin DocumentRoot "/home/httpd/ona"ĭirectoryIndex index.htm index.html index.php index.php3 default.html index.cgi Also, it's important to note that we only comment the parameters that relate to securityĪnd optimization, and leave all the others to your own research.Įdit the nf file, vi /etc/httpd/conf/nf and add/change: The following configuration example is a minimal working configuration file for Apache, with SSL support. A lot options exist, and it's important to read the documentation that comes with Apache for more information on different settingsĪnd parameters. The nf file is the main configuration file for the Apache web server.