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
condor_chirp ulog Message
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 = truein 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).
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
To append the message "Hello World" to the user log, run
% condor_chirp ulog "Hello World"
condor_chirp will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
See the Condor Version 7.2.5 Manual or http://www.condorproject.org/license for additional notices.