I would prefer that the tool work in the presence or absence of FileInstall, and I would prefer that it only deal with the Config Admin service.
On Thu, Nov 19, 2009 at 3:41 PM, Richard S. Hall <[email protected]>wrote: > Why not have your browser-based tool simply dump the changes into the cfg > files managed by File Install? > > -> richard > > > On 11/19/09 5:48 PM, Gerry Woods wrote: > >> We have what may be an unusual situation. We initialize our config admin >> state using .cfg files picked up and deployed by FileInstall. Users may >> then use a browser-based tool to modify these configurations. >> Unfortunately, any modifications made by the user are wiped out when we >> restart because FileInstall assumes it is the only source of configuration >> data for the PIDs associated with the files it sees in its watched >> directory. Because of this, we have been forced to use a modified version >> of FileInstall that adds a timestamp to the configuration that can then be >> compared to the last modified time for the .cfg file. I was wondering if >> this is on anyone else's radar, or if there are any plans to correct this >> behavior. >> >> >> >
