On Wed, 2009-09-09 at 10:10 -0400, M. Ranganathan wrote: > > > On Wed, Sep 9, 2009 at 7:26 AM, Alfred Campbell <[email protected]> > wrote: > What is the strategy to deal with upgrades from 4.0 to 4.2 and > openfire? > Basically how does a site who has upgrade from 4.0 to 4.2 make > openfire > work post upgrade? > > Ideally it would be just goto the server roles screen and add > it.. > However I am pretty sure it won't even install on an upgrade > so I > believe there maybe some work here. > > > > > There is some code in sipxecs-setup that needs to be run for the > databases to be set up. If this step is not normally done on upgrade, > I can extract the necessary code and make it available to the upgrade > script tor run.
That code almost certainly should not be in sipxecs-setup in the first place - it should be in a startup script. The sipxecs-setup is not intended to be a general setup mechanism: it should be only the bare minimum needed to get the system to the point where sipXconfig and sipXsupervisor can start and begin configuring services. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
