The install process for Wildfire 2.4.3 overwrote the conf/wildfire.xml without making a backup copy that I can find… I had to repeat the a good bit of the Install process.
I am concern that other customizaton might have been lost.
Feature/Change Request **
Always backup of any configuration data before changing/overlaying in an upgrade process. Perhaps, a “backup” directory to keep “before” copies of all configure file changes.
Perhaps a third state “” to trigger a upgrade during start that will lead the “admin” account through a update process.
This must be a difference between the RPM and Windows EXE. I’'m going to try a different setting in the installer tool to see if I can work around the issue. Would you be willing to try a new RPM to see if it resolves the issue once I build it?
IMHO, lots of rpm activity is done without much human interaction ( I am at this moment doing a yum update that is refreshing 378 rpm packages on one of my systems ) and a RPM post install process with prompts is troublesome.
I made the change in the installer but it doesn’‘t seem to work with the RPM in our testing. Since we’‘re using a tool to automatically build the RPM, I’‘m a bit stumped. I’'m going to email the tool vendor to find out if this is a known issue.