On 03/27/2010 03:46 AM, Joseph Bester wrote: > That model is not supported by 5.0.0. > > Try this patch. It uses the DN of the certificate to come up with a > semi-unique token that is appended to the service tag. Jobs with > different tags will run in separate job managers and won't deal with > each other's creds.
Hi Joe, Thank you very much - both for the reply confirming it could not work and for a patch making it work. I have applied the patch and with brief testing, it appears to work all fine and fixes our problem. We would do more thorough testing over this (and maybe next week). Yuriy, who's doing most of the work on the client side of the job submission (and who found the issue) is on training this week. We'll report again when we do more testing - but for now, the patch is working all fine. Thanks again for the prompt and very helpful response. Do you think the patch could be integrated in future releases (and maybe, as JP suggests, be the default behavior) ? In the Australia's and New Zealand's grid, we would be so far relying on this behavior. The bulk of our production grid infrastructure is on shared accounts, and we are only trialing out pooled accounts. Cheers, Vladimir > > Joe -- Vladimir Mencl, Ph.D. E-Research Services and Systems Consultant BlueFern Supercomputing Services University of Canterbury Private Bag 4800 Christchurch 8140 New Zealand http://www.bluefern.canterbury.ac.nz mailto:[email protected] Phone: +64 3 364 3012 Mobile: +64 21 997 352 Fax: +64 3 364 2332
