Atlas-connect-l mailing list

[Ilija Vukotic <ivukotic AT uchicago.edu>]

Hi,

Yes the standard way to do this is to send a proxy together with the job to a worker node.

If you look at the tutorial (you can set it up using command: tutorial FAX)

you will see a relevant example will be in the directory SkimSlimT3Large. 

There job submission script has this line:

transfer_input_files = filter-and-merge-d3pd.py,/tmp/x509up_u21183,inputFileListLarge,branchesList,cutCode

it is important that script executed has line equivalent to this:

export X509_USER_PROXY=x509up_u21183

so that the job knows where to look for the proxy.

Best regards,
Ilija

On Jan 9, 2014, at 12:47 , Dr. Harinder Singh Bawa <harinder.singh.bawa AT gmail.com> wrote:

Hello all,

Happy New year.

I have a question if somebody can answer would be appreciated. Currently I have a condor script which I run on Fresno-T3 which setup the environment on each node(ROOT) and compiles and run the job and send me output back to my area. The point is that my input and output data path is pointing to local dir.

The same I am trying to run on ATLASConnect. I thought I can use FAX system to transfer input file from the grid to the node where job is running BUT I see there would be a problem that to do this, I need voms-proxy to be setup on each node which requires passphrase. 

Or I can do is to include my proxy in the path and send it with my job. $X509_USER_PROXY

Do you have any better/simpler  idea than this?

Thanks

--

Dr. Harinder Singh Bawa

                                          
[web][facebook][youtube][twitter]

_______________________________________________
Atlas-connect-l mailing list
Atlas-connect-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/atlas-connect-l