AFS
From FarmShare
| Line 24: | Line 24: | ||
*https://itservices.stanford.edu/service/kerberos/user_guide/how | *https://itservices.stanford.edu/service/kerberos/user_guide/how | ||
*http://fnal.gov/docs/strongauth/user.html | *http://fnal.gov/docs/strongauth/user.html | ||
| + | |||
| + | ==keeping your tokens for more than 24hrs== | ||
| + | If you're using cardinal/corn, you should use "keeptokens" per https://itservices.stanford.edu/service/afs/learningmore/tokens | ||
| + | |||
| + | If you're submitting to the barleys (from the corns), you should _not_ use keeptokens, as the AUKS/SGE integration will handle the krenew/aklog process for you. You should see something like "Auks API request succeeded." when you run qsub. | ||
Revision as of 14:59, 9 November 2011
AFS is now available on the barley machines. You'll want to ensure you have your Kerberos ticket on corn-image-new first.
To obtain and cache Kerberos ticket-granting ticket:
kinit
To list cached Kerberos tickets:
klist
Next, you'll want to ensure you have a valid AFS token.
To obtain tokens for authentication to AFS:
aklog
To display the issuer's tokens:
tokens
Then you can just submit jobs to the resource manager, and the jobs will be able to read/write to/from your AFS directories.
To submit a batch job to Grid Engine:
echo "sleep 3600" | qsub
A simple, complete example:
ssh corn-image-new kinit aklog echo "sleep 3600" | qsub
Links
- https://itservices.stanford.edu/service/kerberos/user_guide/how
- http://fnal.gov/docs/strongauth/user.html
keeping your tokens for more than 24hrs
If you're using cardinal/corn, you should use "keeptokens" per https://itservices.stanford.edu/service/afs/learningmore/tokens
If you're submitting to the barleys (from the corns), you should _not_ use keeptokens, as the AUKS/SGE integration will handle the krenew/aklog process for you. You should see something like "Auks API request succeeded." when you run qsub.
