Hi
Please do not forget the principle of passive stability when talking about the static LDIF files.
Some values in the static LDIF files are what are printed when the dynamic components fail to execute correctly. In general -- not always, but in general -- a dynamic component failing to execute correctly is a sign that something is wrong. And if something is wrong, it is in general a good idea not to attract jobs to your site. The normally-overwritten static LDIF values are chosen to discourage job submission. Which is ok because if a site is working correctly, these static LDIF values never get printed.
So please do not request to have "reasonable" values in the static LDIF files so that your site will appear OK if the dynamic scripts fail. The solution is to understand why the dynamic scripts fail (they should not) and fix them. Reasonable values in the static LDIF prevent the outside world from realizing that your site is broken and facilitate the formation of black holes ...
JT
On Oct 12, 2012, at 10:07 , Andras Hazi wrote:
> Thank you, Massimo.
>
> On 2012-10-12 07:49 Massimo Sgaravatto wrote:
>
>> glite-ce-glue2.conf is a file filled by yaim, which is then used to
>> fill the ldif files only the glue2 objectclasses (i.e. not for
>> static-file-CE.ldif which is for glue1)
>>
>> In glite-ce-glue2.conf the number of logical and physical cpus is
>> filled bu yaim, but not the number of total cpus
>
>
> So why didn't the proper values from glite-ce-glue2.conf appear
> in some of the ldif files? I know, they're overwritten by dynamic
> data, but how can I check where this dynamic data coming from?
>
> Regards
> Andras
|