Hi,
How does EFA handle upgrades of major components like postfix, MailScanner
if the admin has made custom changes to it's config files?
For instance in my setup I use diffent sasl options and different _restrictions.
Will there be .rpmnew files or do the default options of EFA get in again?
thanks in advance
Handling upgrade of custom configurations
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Handling upgrade of custom configurations
Every effort is made to leave config files intact and to modify them in place only as necessary. If they are rpm based upgrades, then yes, you will see rpmnew files.
As an added precaution, copies of files are backed up to /var/EFA/backup prior to update, either in the tarball or the version folders.
As an added precaution, copies of files are backed up to /var/EFA/backup prior to update, either in the tarball or the version folders.
Re: Handling upgrade of custom configurations
thanks for the reply.
good news
good news
Re: Handling upgrade of custom configurations
for what it's worth, I've a fairly customized installation (so many, that I've forgotten all the changes I've made), and except for the changes to the MailScanner web interface I make, everything else appears to remain intact since 3.0.0.7
Quite impressive really.
I suspect that when I do break things, it'll break spectacularly and I'll have to install from scratch and start all over.
Suggestion: document every custom change you make to your system. Don't be like me.
Quite impressive really.
I suspect that when I do break things, it'll break spectacularly and I'll have to install from scratch and start all over.
Suggestion: document every custom change you make to your system. Don't be like me.