Damian wrote:
>Raymond Dans wrote: >> A lot has been done recently to get upgrades from 3.10.x to >3.11.y to >> work properly. >> Part of this work was to add the capability in sipXsupervisor (on >> startup) to determine the status of processes in 3.10.x (by >examining >> and extracting it from the old process.xml files), setting the >> appropriate status of these processes in 3.11.y (under the new >> process-state directory) and then deleting the old process.xml files. >> The problem with this strategy is that when the various >components in >> sipXecs are updated (using yum), the old process.xml files are >> automatically removed by rpm (red hat package manager) since >they not >> present in the new rpm package. > >I am pretty sure that %pre and %post sections of the new >(3.11) RPM spec are executed before the old RPM (3.10) is >being removed. >(http://www.rpm.org/max-rpm/s1-rpm-inside-scripts.html) > >Maybe the proper fix would be to move code that looks for old >process descriptors to that section? > Agreed, the only thing is that a lot of work (not by me) has gone into the upgrade code in sipXsupervisor. That would essentially have to be thrown away and a script then written to do exactly the same thing (i.e. parsing the old process xml file and creating a new process-status file). I have no strong opinion on which way to go but it would be a shame to throw away the work already done. Raymond _______________________________________________ sipx-dev mailing list sipx-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
