Process Model-apache

Relatively thick focus, with MPM encapsulation process model, a variety of strategies can choose

Data structure of MPM

The scoreboard shares the memory and holds the status information of the child process, mainly for the parent process to control the subprocess.
Each time a task is executed, the child process checks to see if it is the same family as the running main process, otherwise gracefully exits. (Running_generation family Number)
Describes threads (in child processes) Information: State, Access, run

Thread connection Information

To know the state of the system, traverse the scoreboard
Terminate the communication pipeline (Pipe of Death)

Process Model
Prefork
Leader/follow
Listener (Leader, worker, idle person)
Worker
Mixed processes and Threads: multiple threads under child processes

Each process has a listening thread. Mutually exclusive to the Accept_mutex.

(Too many processes to start, add sleep Gap)

WinNT MPM
   multithreading + completion port signal Model
   
   
       Listening The thread user listens, is not responsible for connection processing, the worker thread is responsible for connection requests only; Roles can be exchanged
      ap_mpm_pod_check
      
strong> Signal Processing
Exit
     sigterm
    sigwinch
 & Nbsp;  sigint
Non-graceful reboot
    sighup
Graceful Start
    sigusr
Ignore
    sigpipe