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 ? Will it be a valid approach if somehow can we make sipXsupervisor to start without the need of sipxsupervisor-config.in ? Thanks, Mircea _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
