archive-fr.com » FR » O » OBSPM.FR

Total: 155

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • mpm_netware - Apache HTTP Server
    several spare or idle worker threads which stand ready to serve incoming requests In this way clients do not need to wait for a new child threads to be spawned before their requests can be served The StartThreads MinSpareThreads MaxSpareThreads and MaxThreads regulate how the main thread creates worker threads to serve requests In general Apache is very self regulating so most sites do not need to adjust these directives from their default values Sites with limited memory may need to decrease MaxThreads to keep the server from thrashing spawning and terminating idle threads More information about tuning process creation is provided in the performance hints documentation MaxRequestsPerChild controls how frequently the server recycles processes by killing old ones and launching new ones On the NetWare OS it is highly recommended that this directive remain set to 0 This allows worker threads to continue servicing requests indefinitely Directives Listen ListenBacklog MaxMemFree MaxRequestsPerChild MaxSpareThreads MaxThreads MinSpareThreads SendBufferSize StartThreads ThreadStackSize See also Setting which addresses and ports Apache uses MaxThreads Directive Description Set the maximum number of worker threads Syntax MaxThreads number Default MaxThreads 2048 Context server config Status MPM Module mpm netware The MaxThreads directive sets the desired maximum number worker

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/mpm_netware.html (2015-11-16)
    Open archived version from archive


  • mpmt_os2 - Apache HTTP Server
    main parent process and a small static number of child processes The parent process s job is to manage the child processes This involves spawning children as required to ensure there are always StartServers processes accepting connections Each child process consists of a a pool of worker threads and a main thread that accepts connections and passes them to the workers via a work queue The worker thread pool is

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/mpmt_os2.html (2015-11-16)
    Open archived version from archive

  • perchild - Apache HTTP Server
    their default values The maximum number of clients that may be served simultaneously is determined by multiplying the number of server processes that will be created NumServers by the maximum number of threads created in each process MaxThreadsPerChild While the parent process is usually started as root under Unix in order to bind to port 80 the child processes and threads are launched by Apache as a less privileged user The User and Group directives are used to set the privileges of the Apache child processes The child processes must be able to read all the content that will be served but should have as few privileges beyond that as possible In addition unless suexec is used these directives also set the privileges which will be inherited by CGI scripts MaxRequestsPerChild controls how frequently the server recycles processes by killing old ones and launching new ones Working with different user IDs The perchild MPM adds the extra ability to specify that particular processes should serve requests under different user IDs These user IDs can then be associated with specific virtual hosts You have to use one ChildPerUserID directive for every user group combination you want to be run Then you can tie particular virtual hosts to that user and group IDs The following example runs 7 child processes Two of them are run under user1 group1 The next four are run under user2 group2 and the remaining process uses the User and Group of the main server Global config NumServers 7 ChildPerUserID user1 group1 2 ChildPerUserID user2 group2 4 Using unbalanced numbers of processes as above is useful if the particular virtual hosts produce different load The assignment to the virtual hosts is easily done as in the example below In conclusion with the example above the following assumes that server2 has to serve about twice of the hits of server1 Example NameVirtualHost VirtualHost ServerName fallbackhost no assignment use fallback VirtualHost VirtualHost ServerName server1 AssignUserID user1 group1 VirtualHost VirtualHost ServerName server2 AssignUserID user2 group2 VirtualHost AssignUserID Directive Description Tie a virtual host to a user and group ID Syntax AssignUserID user id group id Context virtual host Status MPM Module perchild Tie a virtual host to a specific user group combination Requests addressed to the virtual host where this directive appears will be served by a process running with the specified user and group ID The user and group ID has to be assigned to a number of children in the global server config using the ChildPerUserID directive See the section above for a configuration example ChildPerUserID Directive Description Specify user ID and group ID for a number of child processes Syntax ChildPerUserID user id group id num children Context server config Status MPM Module perchild Specify a user ID and group ID for a number of child processes The third argument num children is the number of child processes to start with the specified user and group It does not represent a specific child number In order to use

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/perchild.html (2015-11-16)
    Open archived version from archive

  • prefork - Apache HTTP Server
    User Topics How it Works See also Setting which addresses and ports Apache uses How it Works A single control process is responsible for launching child processes which listen for connections and serve them when they arrive Apache always tries to maintain several spare or idle server processes which stand ready to serve incoming requests In this way clients do not need to wait for a new child processes to be forked before their requests can be served The StartServers MinSpareServers MaxSpareServers and MaxClients regulate how the parent process creates children to serve requests In general Apache is very self regulating so most sites do not need to adjust these directives from their default values Sites which need to serve more than 256 simultaneous requests may need to increase MaxClients while sites with limited memory may need to decrease MaxClients to keep the server from thrashing swapping memory to disk and back More information about tuning process creation is provided in the performance hints documentation While the parent process is usually started as root under Unix in order to bind to port 80 the child processes are launched by Apache as a less privileged user The User and Group directives are used to set the privileges of the Apache child processes The child processes must be able to read all the content that will be served but should have as few privileges beyond that as possible MaxRequestsPerChild controls how frequently the server recycles processes by killing old ones and launching new ones MaxSpareServers Directive Description Maximum number of idle child server processes Syntax MaxSpareServers number Default MaxSpareServers 10 Context server config Status MPM Module prefork The MaxSpareServers directive sets the desired maximum number of idle child server processes An idle process is one which is not handling a request If

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/prefork.html (2015-11-16)
    Open archived version from archive

  • threadpool - Apache HTTP Server
    work as expected This is an experimental variant of the standard worker MPM Rather than queuing connections like the worker MPM the threadpool MPM queues idle worker threads and hands each accepted connection to the next available worker The threadpool MPM can t match the performance of the worker MPM in benchmark testing As of 2 0 39 some of the key load throtting concepts from the threadpool MPM have

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/threadpool.html (2015-11-16)
    Open archived version from archive

  • mpm_winnt - Apache HTTP Server
    winnt Available Languages de en ja Description This Multi Processing Module is optimized for Windows NT Status MPM Module Identifier mpm winnt module Source File mpm winnt c Summary This Multi Processing Module MPM is the default for the Windows NT operating systems It uses a single control process which launches a single child process which in turn creates threads to handle requests Directives CoreDumpDirectory Listen ListenBacklog MaxRequestsPerChild PidFile ScoreBoardFile

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/mpm_winnt.html (2015-11-16)
    Open archived version from archive

  • mod_access - Apache HTTP Server
    HostnameLookups directive It will do a reverse DNS lookup on the IP address to find the associated hostname and then do a forward lookup on the hostname to assure that it matches the original IP address Only if the forward and reverse DNS are consistent and the hostname matches will access be allowed A full IP address Example Allow from 10 1 2 3 An IP address of a host allowed access A partial IP address Example Allow from 10 1 The first 1 to 3 bytes of an IP address for subnet restriction A network netmask pair Example Allow from 10 1 0 0 255 255 0 0 A network a b c d and a netmask w x y z For more fine grained subnet restriction A network nnn CIDR specification Example Allow from 10 1 0 0 16 Similar to the previous case except the netmask consists of nnn high order 1 bits Note that the last three examples above match exactly the same set of hosts IPv6 addresses and IPv6 subnets can be specified as shown below Allow from fe80 a00 20ff fea7 ccea Allow from fe80 a00 20ff fea7 ccea 10 The third format of the arguments to the Allow directive allows access to the server to be controlled based on the existence of an environment variable When Allow from env env variable is specified then the request is allowed access if the environment variable env variable exists The server provides the ability to set environment variables in a flexible way based on characteristics of the client request using the directives provided by mod setenvif Therefore this directive can be used to allow access based on such factors as the clients User Agent browser type Referer or other HTTP request header fields Example SetEnvIf User Agent KnockKnock 2 0 let me in Directory docroot Order Deny Allow Deny from all Allow from env let me in Directory In this case browsers with a user agent string beginning with KnockKnock 2 0 will be allowed access and all others will be denied Deny Directive Description Controls which hosts are denied access to the server Syntax Deny from all host env env variable host env env variable Context directory htaccess Override Limit Status Base Module mod access This directive allows access to the server to be restricted based on hostname IP address or environment variables The arguments for the Deny directive are identical to the arguments for the Allow directive Order Directive Description Controls the default access state and the order in which Allow and Deny are evaluated Syntax Order ordering Default Order Deny Allow Context directory htaccess Override Limit Status Base Module mod access The Order directive controls the default access state and the order in which Allow and Deny directives are evaluated Ordering is one of Deny Allow The Deny directives are evaluated before the Allow directives Access is allowed by default Any client which does not match a Deny directive or does match an

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/mod_access.html (2015-11-16)
    Open archived version from archive

  • mod_actions - Apache HTTP Server
    Apache s Handler Use Action Directive Description Activates a CGI script for a particular handler or content type Syntax Action action type cgi script Context server config virtual host directory htaccess Override FileInfo Status Base Module mod actions This directive adds an action which will activate cgi script when action type is triggered by the request The cgi script is the URL path to a resource that has been designated as a CGI script using ScriptAlias or AddHandler The action type can be either a handler or a MIME content type It sends the URL and file path of the requested document using the standard CGI PATH INFO and PATH TRANSLATED environment variables Examples Requests for files of a particular type Action image gif cgi bin images cgi Files of a particular file extension AddHandler my file type xyz Action my file type cgi bin program cgi In the first example requests for files with a MIME content type of image gif will instead be handled by the specified cgi script cgi bin images cgi In the second example requests for files with a file extension of xyz are handled instead by the specified cgi script cgi bin program cgi See also AddHandler Script Directive Description Activates a CGI script for a particular request method Syntax Script method cgi script Context server config virtual host directory Status Base Module mod actions This directive adds an action which will activate cgi script when a file is requested using the method of method The cgi script is the URL path to a resource that has been designated as a CGI script using ScriptAlias or AddHandler The URL and file path of the requested document is sent using the standard CGI PATH INFO and PATH TRANSLATED environment variables Any arbitrary method name may

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/mod_actions.html (2015-11-16)
    Open archived version from archive



  •