httpd.conf been rewritten

Chrysalis

Verified User
Joined
Aug 25, 2004
Messages
1,587
Location
uk
I mentioned in another thread about not wanting httpd.conf to be rewritten, on a server I recently noticed the httpd.conf appears to have reverted to a default config and as a result no longer had a include line to mod security configuration amongst some other changes that had been made. I have not ran ./build rewrite_confs.

So the question is what overwrote my httpd.conf? a recent directadmin update? or does the build script overwrite it on other commands?

Does ./build apache overwrite httpd.conf?
 
Did your exim get updated ?

And just for the future, having a copy of a good exim.conf is very handy
 
Did your exim get updated ?

And just for the future, having a copy of a good exim.conf is very handy

what are you talking about? he has problem with httpd.conf....or did I miss something ? :)
 
No, it's not. Because it won't write needed data for php handlers, and suphp handlers.
 
of course its possible, its not very good if its reverting to template format just because apache is been upgraded. What would be nice is if a question or switch is added to ask to rewrite configs or not. Sort of like when asking to reinstall php dependencies.
 
smtalk,

Does CustomBuild currently make backup's of the configfiles present on the server?
If not that might be a good addition too this already excellent script. Just a simple 'cp httpd.conf httpd.conf.old' or something?
 
Last edited:
Chrysalis, with current options it's not possible to install PHP as CGI or 2 versions of PHP when you have old configuration files.

Daredevil, yes it does backups.
 
Chrysalis, with current options it's not possible to install PHP as CGI or 2 versions of PHP when you have old configuration files.

Daredevil, yes it does backups.

I am talking about when the new config files already exist in custombuild format but then customised afterwards for example to load additional modules.
 
Back
Top