Typically this is because you have changed that config file. What I've found is when maintaining the same version of the apache software I don't need to worry about the config, the config I'm using is just fine. And the up2date install of the new package will not overwrite your current config. If you want you can do a diff on the two to see if there is anything in there other than your changes and apply those if you like. Regards, Drew -----Original Message----- From: codefit [mailto:help@xxxxxxxxxxx] Sent: Tuesday, December 16, 2003 7:21 PM To: psyche-list@xxxxxxxxxx Subject: httpd.conf created as /etc/httpd/conf/httpd.conf.rpmnew on up2date Hi, I just ran up2date to update to the latest errata fix. I got the below warning. Does this mean I need to replace the existing httpd.conf file with httpd.conf.rpmnew ? If so I assume I need to do some copy - paste from old to new to preserve my old web server setup? Thanks for any assistance. 1:gnupg ########################################### [100%] 2:httpd warning: /etc/httpd/conf/httpd.conf created as /etc/httpd/conf/httpd.conf.rpmnew ########################################### [100%] 3:httpd-manual ########################################### [100%] 4:lftp ########################################### [100%] 5:mod_ssl ########################################### [100%] -- Psyche-list mailing list Psyche-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/psyche-list
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
