On Wed, 2008-05-14 at 12:38 -0400, Dale Worley wrote:
> On Wed, 2008-05-14 at 11:16 -0400, Andy Spitzer wrote:
> > Seems to me that /var/sipxdata/sipxpresence/ would be clearer, and
> > easier to update/delete when the sipxpresence is updated in the
> > future.
>
> I followed your pointer and it turns out that there's no "SIPX_*" symbol
> for /var/sipxdata from which to generate "/var/sipxdata/sipxpresence".
> But there *are* 10 SIPX_* symbols for various directories we've put
> under /var/sipxdata! (And it looks like there are two additional
> directories under /var/sipxdata that we use but don't have SIPX_*
> symbols for.) 10 of these 12 directories are undocumented in the
> Filesystem Conventions
> (http://www.sipfoundry.org/sipx-project-processes/sipx-filesystem-conventions.html).
>
> How did we get into this mess???
Now would be a great time to fix it.
Take a look at the mechanism I added to
sipXcommserverLib/include/sipXecs/SipXecsService substitutions in other
components by making the paths available at run time (and they are easy
to override in unit tests).
> But back to the immediate problem -- Should I create yet another SIPX_*
> symbol for the "sipxpresence" directory? It does seem a better location
> than the "sipdb" directory.
I'd say create on that maps to /var/sipxdata (or, more correctly in
autoconf terms ${datadir}/sipxdata ), and then convert the others to use
that as a base too.
--
Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED]
sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs
CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/
http://www.pingtel.com/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
