Re: [sipX-dev] Input on XCF-651 implementation (Restore page from sipXconfig UI)
On Wed, 2007-04-04 at 16:11 -0400, Damian Krzeminski wrote:
> Paul Mossman wrote:
> > Thanks Scott,
> >
> >> 4. The process manager does that as now, executing the normal
> >> sipxconfig.sh startup wrapper script.
> >> 5. The wrapper script sees that there is a file in the special
> >> well-known location; it validates that the indicated file is a
> >> db backup file, and does the restore operation before restarting
> >> sipXconfig.
> >
> > I am planning to combine the notion of File and Database Configuration
> > into an atomic unit, so you Backup/Restore them either together, or
> > not at all. Given this, would it still make sense check for the file
> > in sipxconfig.sh, and not before? Aren't there Configuration Files
> > for services that will have been started before sipXconfig? e.g.
> > proxy-config.in and WatchDog.xml. Or, am I confusing this with the
> > larger sequencing problem?
> I do think you are confusing anything. Since both configuration files and
> database will be restored
> we will have to restart everything. I do not think that causes any sequencing
> problems. You original
> idea of how to implement this still seems right to me.
It is not acceptable to give the sipXconfig UI superuser privileges,
though.
If the sipXconfig application can detect that it has been restarted with
a restored configuration (which may also have restored other
configuration files - seems like a good idea, in fact), then it can
order restarts of any active services after having regenerated those
configurations based on the restored data.
--
Scott Lawrence tel:+1-781-938-5306;ext=162 or sip:slawrence@xxxxxxxxxxx
sipXpbx project coordinator - SIPfoundry http://www.sipfoundry.org/sipX
Chief Technology Officer - Pingtel Corp. http://www.pingtel.com/
