[ Pobierz całość w formacie PDF ]
.In many cases, the operatingsystem will limit the backlog parameter to the listen(2) system call toa smaller number.This limitation varies from one operating systemto the next.Also, note that many operating systems do not use thebacklog exactly as specified, but instead use a number based on (butnormally larger than) that set.Papersize: (US letter)Cropmarks: (AWL repro)84 Chapter 4: Configuring ApacheLockFile http corePath to Lock File for Serialized Connection AcceptsSyntax: pathhttpd.conf.htaccessAuthConfigExample:LimitsOptionsDefault:FileInfoIndexesSince: Apache 1.2The path is used when the server needs to lock the call.This directive should normally be left at its default value.It might bechanged if the log s directory is NFS-mounted, as the lock file mustbe stored on a local disk.The PID of the main server process is auto-matically appended to the file name.For security reasons, you shouldavoid putting this file in a world-writable directory, such as ,because someone could launch a denial-of-service attack and preventthe server from starting by creating a lock file with the same name asthe one the server will try to create.LogLevel http coreLogging LevelSyntax: levelhttpd.conf.htaccessAuthConfigExample:LimitsOptionsDefault:FileInfoIndexesSince: Apache 1.3This directive adjusts the verbosity of the messages recorded in theUse server s error logs (see the directive).The following levelson production webare available, in order of decreasing significance: (emergencies:servers to reducelogging overhead.system is unusable); (action must be taken immediately);(critical conditions); (error conditions); (warning condi-tions); (normal but significant condition); (informationalmessages); and (debugging messages).When a particular levelis specified, messages from all other levels of higher significance willbe reported as well.MaxClients http coreMaximum Number of ClientsSyntax: numberhttpd.conf.htaccessAuthConfigExample:LimitsOptionsDefault:FileInfoIndexesSince: Apache 1.0This directive limits the number of simultaneous HTTP requests thatcan be supported; no more than this number of child server processeswill be created.To configure more than 256 clients, one must edit theentry in and recompile Apache.Any con-nection attempts that exceed the limit will normally bePapersize: (US letter)Cropmarks: (AWL repro)4.3 Configuration Reference 85queued in kernel space, up to a number based on thedirective.Once a child process is freed at the end of a different request,the queued connection will be serviced.MaxKeepAliveRequests http coreMaximum Number of Keep-Alive Requests per ConnectionSyntax: numberhttpd.conf.htaccessAuthConfigExample:LimitsOptionsDefault:FileInfoIndexesSince: Apache 1.2This directive sets the maximum number of HTTP Keep-Alive requestsallowed per established TCP/IP connection when is on.Use 0 to specify an unlimited number of requests.Use high values toobtain maximum server performance.MaxRequestsPerChild http coreMaximum Number of Requests per Server Child ProcessSyntax: numberhttpd.conf.htaccessAuthConfigExample:LimitsOptionsDefault:FileInfoIndexesSince: Apache 1.0This directive sets the maximum number of HTTP requests that an in-dividual server child process can handle.After this number of requests Useis reached, the child process will die.If number is , then the processto control thewill never die automatically.For requests, only the first re- maximum number ofHTTP requests that anquest counts toward this limit.individual server childprocess can handle.MaxSpareServers http coreMaximum Number of Idle Server Child ProcessesSyntax: numberhttpd.conf.htaccessAuthConfigExample:LimitsOptionsDefault:FileInfoIndexesSince: Apache 1.0This directive sets the maximum number of idle server child processes.An idle process is one that is not currently handling a request.If morethan number processes are idle, then the parent process will kill off theexcess processes.MinSpareServers http coreMinimum Number of Idle Server Child ProcessesSyntax: numberhttpd.conf.htaccessAuthConfigExample:LimitsOptionsDefault:FileInfoIndexesSince: Apache 1.0Papersize: (US letter)Cropmarks: (AWL repro)86 Chapter 4: Configuring ApacheThis directive sets the minimum number of idle server child processes.An idle process is one that is not currently handling a request.If fewerthan number processes are idle, then the parent process creates newchildren at a maximum rate of one per second.NameVirtualHost http coreDeclare a Name-based Virtual HostSyntax: host porthttpd.conf.htaccessAuthConfigExample:LimitsOptionsDefault:FileInfoIndexesSince: Apache 1.3This directive is required if you want to configure name-based virtualUse hosts
[ Pobierz całość w formacie PDF ]