Hello SB> Do you have the date/time that you grabbed the source code for the SB> 3.5-SNAPSHOT build that you are using?.
.git/logs/HEAD contains what looks like a timestamp. It translates to: Tue Mar 22 2011 17:12:58 GMT+0000 (GMT) which should be about right, I think. SB> Also, setting the datastream state to inactive/deleted then back to SB> active should trigger an update of the policy index. That works, and with external datastreams too. Thanks. SB> However with managed content FESLPOLICY datastreams, a modification to SB> the datastream content should trigger an immediate change (providing SB> PEP_NOCACHE is true and exported); it sounds like this is not SB> happening for you. The cached version is updated, if I modify the content of a managed datastream - either editing the content or purging and adding again. I was expecting external FESLPOLICY datastreams to be refreshed when the external version was updated. But what I should expect is that datastreams get refreshed if the local copy is modified (managed), or the datastream changes state (managed/external). SB> I'd like to investigate this further in case we have a bug. Now that my expectations are realistic, I think it is working as it is to be expected to. Swithun. -- The University of St Andrews is a charity registered in Scotland: SC013532 ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users