Lee,

Has there been any update to the opt-out documentation?

Thanks,
Jim

Lee Liming wrote:
> Hi,
> 
> This issue applies to many Globus components, so I'm forwarding to a
> rather broad distribution.  I hope this doesn't cause problems for anyone.
> 
>          -- Lee
> 
> 
> Begin forwarded message:
> 
>> From: Jim Basney <jbas...@ncsa.uiuc.edu>
>> Date: July 21, 2009 10:33:41 AM MDT
>> To: usage-st...@globus.org
>> Subject: [usage-stats] documentation for opt-out / configuration of
>> Globus usage statistics
>>
>> Hi,
>>
>> At
>> http://www.globus.org/toolkit/docs/4.2/4.2.1/admin/install/#gtadmin-config-usage-stats
>>
>> it says, "The following components collect usage statistics as outlined
>> here (along with information about how to opt-out)" with a link to
>> http://www.globus.org/toolkit/docs/4.2/4.2.1/Usage_Stats.html
>> but I can't find the information about how to opt-out on that
>> Usage_Stats.html page. There's an "Opt-out" section, but it doesn't
>> describe how.
>>
>> Back on the "Installing GT 4.2.1" page, "Appendix H. Usage Statistics",
>> I see the details listed for each component, and it appears that opting
>> out for all components requires setting GLOBUS_USAGE_OPTOUT=1 in the
>> environment (for C components) and modifying usageStatisticsTargets in
>> $GLOBUS_LOCATION/etc/globus_wsrf_core/server-config.wsdd (for Java
>> components). Is that right? These details are listed under each
>> component, rather than being described as a consistent interface across
>> all Globus components, so maybe there are some components that require a
>> different configuration for opting out? Hopefully not.
>>
>> I suggest documenting the steps for opting out for all Globus components
>> on the Usage_Stats.html page and ensuring that those steps work
>> consistently across all components.
>>
>> It would be nice if the Java components respected the
>> GLOBUS_USAGE_OPTOUT environment variable, rather than requiring
>> different configurations for C and Java components, but I understand
>> that Java 1.4 support for environment variables is lacking.
>>
>> -Jim

Reply via email to