From Anand:
A fix for configure_gip:
> 2. Add back the code in configure_gip that actually checks for this
> variable [OSG_GIP_GUMS] before enabling GUMS monitoring. In this way
>admins can just set OSG_GIP_GUMS to 0 by hand and disable this
> monitoring.
Also:
> This is a minor update to osg-info-dynamic-condor, fixes the issue
> raised in footprints ticket 4163.
Problem report from ticket 4163:
> It seems that
> /afs/atlas.umich.edu/OSG/lcg/libexec/osg-info-dynamic-condor
> fails because of the way the condor parameter
> GROUP_PRIO_FACTOR_group_ligo is defined in condor_config.local.
>
> This is possibly related to the GIP configuration scripts.
> Unfortunately, I don't know how the GROUP_PRIO_FACTOR_group_ligo
> parameter is used. The relevant error in the output is
>
> [gate01:~]# cat /tmp/err
> Not defined: GROUP_PRIO_FACTOR_group_ligo
> Use of uninitialized value in numeric le (<=) at
> /afs/atlas.umich.edu/OSG/lcg/libexec/osg-info-dynamic-condor line 83,
> <VOFILE> line 80.
Anand's respoonse in the Footprints ticket:
>2. As for the error you see with GROUP_PRIO_FACTOR_group_ligo, I am not
>sure why it would occur. The only way I see this error occurring is if
>%condor_config_val GROUP_NAMES returns ligo in its list of VO, but there
>is no corresponding query %condor_config_val
>GROUP_PRIO_FACTOR_group_ligo doesnot return a valid entry. This can be
>easily fixed, and I will get it fixed in the new release.