This is an outdated version of the HTCondor Manual. You can find current documentation at http://htcondor.org/manual.
next up previous contents index
Next: condor_compile Up: 12. Command Reference Manual Previous: condor_chirp   Contents   Index

Subsections


condor_cod

manage COD machines and jobs

Synopsis

condor_cod [-help $\vert$ -version]

condor_cod request [-pool centralmanagerhostname[:portnumber] $\vert$ -name scheddname ]$\vert$ [-addr "<a.b.c.d:port>"] [[-help $\vert$ -version] $\vert$ [-debug $\vert$ -timeout N $\vert$ -classad file] ] [-requirements expr] [-lease N]

condor_cod release -id ClaimID [[-help $\vert$ -version] $\vert$ [-debug $\vert$ -timeout N $\vert$ -classad file] ] [-fast]

condor_cod activate -id ClaimID [[-help $\vert$ -version] $\vert$ [-debug $\vert$ -timeout N $\vert$ -classad file] ] [-keyword string $\vert$ -jobad filename $\vert$ -cluster N $\vert$ -proc N $\vert$ -requirements expr]

condor_cod deactivate -id ClaimID [[-help $\vert$ -version] $\vert$ [-debug $\vert$ -timeout N $\vert$ -classad file] ] [-fast]

condor_cod suspend -id ClaimID [[-help $\vert$ -version] $\vert$ [-debug $\vert$ -timeout N $\vert$ -classad file] ]

condor_cod renew -id ClaimID [[-help $\vert$ -version] $\vert$ [-debug $\vert$ -timeout N $\vert$ -classad file] ]

condor_cod resume -id ClaimID [[-help $\vert$ -version] $\vert$ [-debug $\vert$ -timeout N $\vert$ -classad file] ]

condor_cod delegate_proxy -id ClaimID [[-help $\vert$ -version] $\vert$ [-debug $\vert$ -timeout N $\vert$ -classad file] ] [-x509proxy ProxyFile]

Description

condor_cod issues commands that manage and use COD claims on machines, given proper authorization.

Instead of specifying an argument of request, release, activate, deactivate, suspend, renew, or resume, the user may invoke the condor_cod tool by appending an underscore followed by one of these arguments. As an example, the following two commands are equivalent:

    condor_cod release -id "<128.105.121.21:49973>#1073352104#4"
    condor_cod_release -id "<128.105.121.21:49973>#1073352104#4"
To make these extended-name commands work, hard link the extended name to the condor_cod executable. For example on a Unix machine:
ln condor_cod_request condor_cod

The request argument gives a claim ID, and the other commands (release, activate, deactivate, suspend, and resume) use the claim ID. The claim ID is given as the last line of output for a request, and the output appears of the form:

ID of new claim is: "<a.b.c.d:portnumber>#x#y"
An actual example of this line of output is
ID of new claim is: "<128.105.121.21:49973>#1073352104#4"

The HTCondor manual has a complete description of COD.

Options

-help
Display usage information
-version
Display version information
-pool centralmanagerhostname[:portnumber]
Specify a pool by giving the central manager's host name and an optional port number
-name scheddname
Send the command to a machine identified by scheddname
-addr "<a.b.c.d:port>"
Send the command to a machine located at "<a.b.c.d:port>"
-lease N
For the request of a new claim, automatically release the claim after N seconds.
request
Create a new COD claim
release
Relinquish a claim and kill any running job
activate
Start a job on a given claim
deactivate
Kill the current job, but keep the claim
suspend
Suspend the job on a given claim
renew
Renew the lease to the COD claim
resume
Resume the job on a given claim
delegate_proxy
Delegate an X509 proxy for the given claim

General Remarks

Examples

Exit Status

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

Author

Center for High Throughput Computing, University of Wisconsin-Madison

Copyright

Copyright © 1990-2017 Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0.
next up previous contents index
Next: condor_compile Up: 12. Command Reference Manual Previous: condor_chirp   Contents   Index