Here's the problem:
You add a module to Apache.
Then, later, Apache is restarted and fails because the added module doesn't get handled properly and Apache fails to start due to the reference to the no longer present Apache module.
Apparently, this is also a problem when Cpanel or PHP are updated.
What I want to know is:
How do we setup both Apache and Cpanel so that it is easier to keep track of modules added to Cpanel, PHP, Apache, as well as other configuration options so that the modules and settings are retained, loaded into the system and do not cause Apache restarts to fail?
For example:
I installed Web Dav. Then later, Apache was restarted. The Web Dav modules weren't loaded and Apache failed to start.
Geoff
You add a module to Apache.
Then, later, Apache is restarted and fails because the added module doesn't get handled properly and Apache fails to start due to the reference to the no longer present Apache module.
Apparently, this is also a problem when Cpanel or PHP are updated.
What I want to know is:
How do we setup both Apache and Cpanel so that it is easier to keep track of modules added to Cpanel, PHP, Apache, as well as other configuration options so that the modules and settings are retained, loaded into the system and do not cause Apache restarts to fail?
For example:
I installed Web Dav. Then later, Apache was restarted. The Web Dav modules weren't loaded and Apache failed to start.
Geoff