Woof! On Tue, 28 Oct 2008 13:16:29 -0400, Beeton, Carolyn (CAR:9D60) <[EMAIL PROTECTED]> wrote:
> Can you check whether your > domain-config contains SUPERVISOR_PORT and CONFIG_HOST? If not, it > needs to be regenerated (sipx-setup will do it). No, it does not. And sipxconfig cannot regenerate domain-config for me, as it's a chicken and egg problem that sipxconfig needs sipxsupervisor to regenerate files, and the file it needs to regenerate isn't allowing that. Something about requiring domain-config to exist and be valid before allowing the replication of domain-config seems wrong to me. Having sipx-setup generate one first, that is then overwritten by sipxconfig's version, seems to bring us right back to where we were when we had "checked in" versions of config files for initial startup before sipxconfig would run. What is so imporant in domain-config that sipxsupervisor refuses to accept configuration unless it exists? I would prefer to see sipxsupervisor "limp" along without it until such time as sipxconfig can replicate it. Having two places creating the same file wasn't a good idea before, and it isn't now. One approch might be to have sipxsupervisor use domain-config if it exists, and fallback to whatever sipx-setup generates IN SOME OTHER FILE if it doesn't. I'm wary about running sipx-setup on my devel system...is it safe to run on a working development machine, or will it overwrite critical files? --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
