On Fri, 2009-04-10 at 17:07 -0400, Damian Krzeminski wrote: > Scott Lawrence wrote: > > On Fri, 2009-04-10 at 12:26 -0400, Andy Spitzer wrote: > >> Woof! > >> > >> On Fri, 10 Apr 2009 12:04:37 -0400, Scott Lawrence > >> <[email protected]> wrote: > >> > >>> Cons: > >>> * If we write the file in the setup, then sipXconfig has to read > >>> it to figure out the state. > >> Actually, all you have to do is somehow tell sipXconfig to create the > >> file in a given state,...like an entry in the database, or a command > >> line switch. Let sipXconfig gen the file, but setup can tell > >> sipXconfig to gen the file. > > > > I was thinking about how to add this to 4.0 - it's a bit of a problem since > we do not really have a good support for services that are not managed by > sipx-supervisor. We cannot reuse nice infrastructure for service plugins here. > > But we could pretend for a moment that it is sipxconfig configuration file. > Just as you did adding it to the descriptor. And generate if with > everything else. > > > > I hadn't thought of that... > > > > Some time after sipXconfig writes the file, something has to (re)start > > the system-level 'phonelogd' service though in order to see the new > > configuration (which we could do with another wrapper). > > > > > > I would say: if you change this value, sipXconfig will would config file > but admin would need to restart the system (or restart phonelogd if they > are os literate). > > If you want to pass some info from sipxecs-setup to sipxconfig: maybe we > can use the file that you and Kevin came up with (don't remember the name > at the moment).
My own opinion is that requiring a system restart to do this is ok. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
