Hi Ben,
I suspect it depends on the YAIM version. I'm on SL5 and use
glite-yaim-dpm-4.0.9-3 and don't have this problem. If you cannot
upgrade you could always use the post mechanism in yaim to alter the
configuration.
http://en.wikipedia.org/wiki/Yaim#YAIM.27s_directory_structure
and just write a post function that does:
sed -i.old 's/--legacy//' /opt/glite/etc/gip/provider/se-dpm
mv /opt/glite/etc/gip/provider/se-dpm.old <wherever>/backup/
I can't remember if it is the provider or the plugin bit or both that
executes all the files in the directory so it's better to remove the
saved copy from the directory.
In this way when you rerun yaim the legacy bit is removed by yaim itself.
cheers
alessandra
On 11/03/2011 15:41, Ben Waugh wrote:
> Thanks Alessandra.
>
> Removing --legacy from the call to dpm-listspaces in
> /opt/glite/etc/gip/provider/se-dpm works temporarily, but the file is
> overwritten when I run YAIM.
>
> Any idea how to make this change persist?
>
> Cheers,
> Ben
>
>
> On 11/03/11 08:35, Alessandra Forti wrote:
>> Hi Ben,
>>
>> dpm-listspaces is started with a --legacy switch it needs to be removed.
>>
>> You can look at Sheffield ticket for more information.
>>
>> https://gus.fzk.de/ws/ticket_info.php?ticket=68093
>>
>> cheers
>> alessandra
>>
>> On 10/03/2011 23:06, Ben Waugh wrote:
>>> Hi All,
>>>
>>> I'm looking at a GGUS ticket
>>> <https://gus.fzk.de/ws/ticket_info.php?ticket=68092> and at the
>>> results of an LDAP query of the UCL-HEP site BDII and scratching my
>>> head as I try to work out where the published "GlueSACapability:
>>> InstalledOnlineCapacity" comes from and why some SAs instead have
>>> only "GlueSACapability: legacy".
>>>
>>> Is this documented anywhere, or can someone advise me? I'm sure I've
>>> missed something stupid. Is it related to the fact that a couple of
>>> our pool nodes are "DISABLED" or is that a completely separate problem?
>>>
>>> Cheers,
>>> Ben
>>>
>>
>
|