View Single Post
  #1  
Old 26th April 2013, 15:09
Ben Ben is offline
Moderator
 
Join Date: Jul 2006
Posts: 1,029
Thanks: 7
Thanked 62 Times in 56 Posts
Default IPSCFG Upgrade - persistent part of postfix main.cf

Hi guys,

lately I updated my IPSCOnfig to the most recent version, with the effect I was generally aware of, but finally forogt about it, that it backups but recreates some config files.
In my special case, the main.cf, where I added some RBL filters, changed the TLS certificate files and some others.
And I also made this file a bit more human readable with some tabs and linebreaks

So the final question is, what is seen from the upgrade archtitecture a possible solution to detect differences between the current and the new file and e.g. prompt for action, like aptitude does.

I am aware of that things might get complicated it there was a change in the "native" config file ispconfig3 provided between a current and the upated version, when a parameter was additionally extended by an admin.

So my idea woul be to ask the user for what to do, then save the old file as backup, and explicitly NOT restarting the particular service. After the installation the admin gets presented a list with services not startet and config changes that need a manual review.
This would ensure that service do not start with a "broken" configuration, and to manually crawl through the diffs.

Any better suggestions?
Reply With Quote
Sponsored Links