apache2-mpm-itk (just mpm-itk for short) is an MPM (Multi-Processing Module) for the Apache web server. mpm-itk allows you to run each of your vhost under a separate uid and gid—in short, the scripts and configuration files for one vhost no longer have to be readable for all the other vhosts.

What are the best alternatives to MPM-ITK?

If mpm-itk does not suit your tastes, here are some alternatives: If you only run CGI scripts, suexecwill probably solve most of your problems with any MPM. Similarly, suPHPprovides a PHP-only solution. If you are on Solaris, mod_privileges, part of Apache since 2.4, provides functionality somewhat like mpm-itk.

What are the new configuration settings over the MPM?

The new configuration settings over the prefork MPM are: AssignUserID: Takes two parameters, uid and gid (or really, user name and group name; use “# ” if you want to specify a raw uid); specifies what uid and gid the vhost will run as (after parsing the request etc., of course).

How do I enable PHP modules for Apache2?

If you install the PHP4 or PHP5 modules for Apache2 then they will automatically enable themselves.If you have any problem you can use the following commands to enable php modules manually. This will complete the installation.

What is the MPM event in Apache HTTP?

By combining the MPM Event in Apache HTTP with the PHP FastCGI Process Manager (PHP-FPM) a website can load faster and handle more concurrent connections while using fewer resources.

How to configure the MPM Prefork module in DirectAdmin?

Below you can find an example configuration for the MPM prefork module: To change the MPM in plain RHEL or Debian based systems replace mpm_prefork_module with mpm_worker_module or mpm_event_module, respectively. In DirectAdmin the MPM module can be selected by using Custombuild or by editing /usr/local/directadmin/custombuild/options.conf