next up previous contents index
Next: condor_ cod Up: 9. Command Reference Manual Previous: condor_ checkpoint   Contents   Index

Subsections


condor_ chirp

Access files or job ClassAd from an executing job

Synopsis

condor_ chirp [-help]

condor_ chirp fetch RemoteFileName LocalFileName

condor_ chirp put [-mode mode] [-perm UnixPerm] LocalFileName RemoteFileName

condor_ chirp remove RemoteFileName

condor_ chirp get_job_attr JobAttributeName

condor_ chirp set_job_attr JobAttributeName AttributeValue


Description

condor_ chirp is run from a user job while executing. It accesses files or job ClassAd attributes on the submit machine. Files can be read, written or removed. Job attributes can be read, and most attributes can be updated.

Descriptions using the terms local and remote are given from the point of view of the executing program.

If the input file name for put is a dash, condor_ chirp uses standard input as the source. If the output file name for fetch is a dash, condor_ chirp writes to standard output instead of a local file.

Jobs that use condor_ chirp must have the attribute WantIOProxy set to True in the job ad. To do this, place

+WantIOProxy = true
in the submit description file for the job.

condor_ chirp only works for jobs run in the vanilla, mpi, parallel and java universes.

The optional -mode mode argument is one or more of the following characters describing the RemoteFileName file.

The optional -perm UnixPerm argument describes the file access permissions in a Unix format (for example, 660).

Options

-help
Display usage information and exit.
fetch
Copy the RemoteFileName from the submit machine to the execute machine.
remove
Remove the RemoteFileName file from the submit machine.
put
Copy the LocalFileName from the execute machine to the submit machine. Perm is the unix permission to open the file with.
get_job_attr
Prints the named job ClassAd attribute to standard output.
set_job_attr
Sets the named job ClassAd attribute with the given attribute value.

Examples

To copy a file from the submit machine to the execute machine while the user job is running, run

% condor_chirp fetch remotefile localfile

To print to standard output the value of the Requirements expression from within a running job, run

% condor_chirp get_job_attr Requirements

Note that the remote (submit-side) directory path is relative to the submit directory, and the local (execute-side) directory is relative to the current directory of the running program.

To append the word "foo" to a file on the submit machine, run

% echo foo | condor_chirp put -mode wat - RemoteFile

Exit Status

condor_ chirp will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Author

Condor Team, University of Wisconsin-Madison

Copyright

Copyright © 1990-2007 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. No use of the Condor Software Program is authorized without the express consent of the Condor Team. For more information contact: Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

U.S. Government Rights Restrictions: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable, Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

See the Condor Version 6.8.7 Manual for additional notices.


next up previous contents index
Next: condor_ cod Up: 9. Command Reference Manual Previous: condor_ checkpoint   Contents   Index
condor-admin@cs.wisc.edu