On Thu, 2008-10-16 at 17:36 +0300, Mircea Carasel wrote: > Hi, > I was about to post a patch for XCF-2864 when I found out that there are > problems with regard to sipxsupervisor-config.in.in and > sipxsupervisor-config.in cleanup > > If I delete sipxsupervisor-config.in from etc/sipbpbx and restart the > server - the sipxsupervisor process will not start correctly and none of > the other services will start (which is reasonable). > This leads to the fact that sipxsupervisor-config will never get > generated by sipXconfig > > I think that we have a race condition here: > 1. sipXsupervisor cannot start if sipxsupervisor-config.in is not found > 2. the sipXconfig process that handles sipxsupervisor-config generation > cannot start if sipXsupervisor does not start in the first place > > Any thoughts - what can be done about this scenario ?
Ultimately I'd like to change sipXsupervisor so that it does not require that file, but in the mean time I'll have to work around it in the sipx-setup bootstrap start script (part of the replacement for sipx_reset_cd, see XECS-1788]. I hope to get some version of that checked in today or tomorrow. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
