On Tue, 2008-11-11 at 12:56 -0500, Beeton, Carolyn (CAR:9D60) wrote:
> > -----Original Message-----
> > From: Lawrence, Scott (BL60:9D30)
> > Sent: Tuesday, November 11, 2008 10:41 AM
> > To: Beeton, Carolyn (CAR:9D60)
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: [sipX-dev] location of process config version files
> >
> >
> > On Tue, 2008-11-11 at 10:15 -0500, Carolyn Beeton wrote:
> > > Are the process config version files intended to be under
> > > /var/sipxdata/process-cfgver or /var/sipxecs/process-cfgver?
> > > The code is actually using the ones under
> > /var/sipxdata/process-cfgver
> > > (i.e. $VARDIR/process-cfgver) but the makefiles and rpm
> > install create
> > > /var/sipxecs/process-cfgver.
> >
> > The right location is /var/sipxecs/process-*
> >
> >
> >
> In that case the supervisor code that does this:
>
> OsPath
> persistentConfigVersionPath(SipXecsService::Path(SipXecsService::VarDirT
> ype,
> SipxProcessConfigVersionDir)
> + OsPath::separator + data());
>
> is wrong, because VarDirType points to var/sipxdata, not var/sipxecs.
> It is putting both the process-states and the process-cfgvers under
> var/sipxdata. "Vardir" is defined to be var/sipxdata.
>
> Can I just back up a bit and ask why we want both a sipxecs and a
> sipxdata under var?
>
> If we do want both, is LocalStateDir the one that is supposed to point
> to var/sipxecs? or do we need to define a new variable in both
> sipXlib.m4 and SipXecsService?
>
> A bit of an aside: Looking at SipXecsService, I wonder if the
> LocalStateDir is wrong (it is also set to SIPX_VARDIR) - it looks to me
> like it should be pointing to /var, not /var/sipxdata. (based on this
> line from sipXlib.m4: AC_SUBST(SIPX_VARDIR,
> [${localstatedir}/sipxdata])). But then LocalStateDirType is used in
> sipXacd/src/ACDAudioManager.cpp where it (possibly?) should be using
> VarDirType...
I'll try to answer the above with a simple principle...
Ideally we should have one directory under the autoconf localstatedir
that has all the state data we need to store (appropriately organized
under subdirectories, of course).
SIPX_VARDIR should point to that top directory, and everything else
should be relative to that.
Back in the real world, we're not there, and it may be too much trouble
to completely fix it now, but I suspect you've found the problem with
process states...
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
