Apache conf distiller = waste of time ???


Well-Known Member
Dec 24, 2003
cPanel Access Level
Root Administrator
Once the changes have been distilled, they will be saved for later conf rebuilds.
I wish this is true but unfortunately, it is not and this is getting really, really irritating, to say the least :mad:

Just an example : I want to disable the directory indexing server wide (why is apache no longer taking the access.conf into consideration, btw ???), so :
1) I change "Options All" to "Options -Indexes" in httpd.conf.
2) I run the distiller.
3) /var/cpanel/conf/apache/main does reflect the change.

According to what Todd said, you would think that EA3 will use /var/cpanel/conf/apache/main for the next rebuild ? You're wrong. Even when recompiling with the previous build, /var/cpanel/conf/apache/main gets reset and the changes are lost.

Now, is there any way to keep these changes so we don't have to redo all the work after each new compilation ???

PS : I'm running WHM 11.11.0 cPanel 11.15.0-C17853


cPanel Development
Staff member
Apr 7, 2006
cPanel Access Level
Root Administrator
Use the Apache Include Editor to make and save those changes. The distiller will save most changes across httpd.conf rebuilds, but rebuilding Apache will over-write them (as you described).