Sometimes smooth execution of a module requires such actions as changing owners (and access permissions) of certain files, making up groups of special users, customizing network settings, etc. These changes are made on the system level, and the module can declare them in a special file. If these modifications of system settings are not necessary, you can skip this step.
If the module requires some modifications in the current system settings, it should contain the file named
httpsd.<module_name>.include in folder
plesk_root_dir>/admin/conf of the module's package. This file contains a shell script that runs system/custom utilities to perform the required modifications.
When Plesk tries to execute a module, it always checks whether the module contains this file at the specified path, and executes the script if the file is found.
Here is the example of this script:
echo 0 > /proc/sys/net/ipv4/ip_forward
@@IPTABLES@@ -P INPUT ACCEPT
@@IPTABLES@@ -P OUTPUT ACCEPT
@@IPTABLES@@ -P FORWARD DROP
if [ -f '@@PRODUCT_ROOT_D@@/var/modules/@@MODULE@@/openvpn.pid' ]; then
kill `cat '@@PRODUCT_ROOT_D@@/var/modules/@@MODULE@@/openvpn.pid'`
rm -f '@@PRODUCT_ROOT_D@@/var/modules/@@MODULE@@/openvpn.pid'
This script executes a set of commands of the
iptables utility, after which the
openvpn.pid module is used to modify network settings.
Thus, if not skipped, this step should result in the file with a shell script created and put to the proper folder of the module package.