1CONDOR_COD(1)                   HTCondor Manual                  CONDOR_COD(1)
2
3
4

NAME

6       condor_cod - HTCondor Manual
7
8       manage COD machines and jobs
9
10
11

SYNOPSIS

13       condor_cod [-help | -version ]
14
15       condor_cod  request [ -pool centralmanagerhostname[:portnumber] | -name
16       scheddname ] | [-addr "<a.b.c.d:port>"] [ [-help | -version ] | [-debug
17       | -timeout N | -classad file ] ] [-requirements expr ] [-lease N ]
18
19       condor_cod release -id ClaimID [ [-help | -version ] | [-debug | -time‐
20       out N | -classad file ] ] [-fast ]
21
22       condor_cod activate -id ClaimID [ [-help  |  -version  ]  |  [-debug  |
23       -timeout  N  |  -classad  file ] ] [-keyword string | -jobad filename |
24       -cluster N | -proc N | -requirements expr ]
25
26       condor_cod deactivate -id ClaimID [ [-help | -version  ]  |  [-debug  |
27       -timeout N | -classad file ] ] [-fast ]
28
29       condor_cod suspend -id ClaimID [ [-help | -version ] | [-debug | -time‐
30       out N | -classad file ] ]
31
32       condor_cod renew -id ClaimID [ [-help | -version ] | [-debug | -timeout
33       N | -classad file ] ]
34
35       condor_cod  resume -id ClaimID [ [-help | -version ] | [-debug | -time‐
36       out N | -classad file ] ]
37
38       condor_cod delegate_proxy -id ClaimID [ [-help | -version ] | [-debug |
39       -timeout N | -classad file ] ] [-x509proxy ProxyFile]
40

DESCRIPTION

42       condor_cod  issues commands that manage and use COD claims on machines,
43       given proper authorization.
44
45       Instead of specifying an argument of request, release, activate,  deac‐
46       tivate,  suspend,  renew, or resume, the user may invoke the condor_cod
47       tool by appending an underscore followed by one of these arguments.  As
48       an example, the following two commands are equivalent:
49
50          condor_cod release -id "<128.105.121.21:49973>#1073352104#4"
51
52          condor_cod_release -id "<128.105.121.21:49973>#1073352104#4"
53
54       To  make these extended-name commands work, hard link the extended name
55       to the condor_cod executable. For example on a Unix machine:
56
57          ln condor_cod_request condor_cod
58
59       The request argument gives a claim ID, and the other commands (release,
60       activate,  deactivate, suspend, and resume) use the claim ID. The claim
61       ID is given as the last line of output for a request,  and  the  output
62       appears of the form:
63
64          ID of new claim is: "<a.b.c.d:portnumber>#x#y"
65
66       An actual example of this line of output is
67
68          ID of new claim is: "<128.105.121.21:49973>#1073352104#4"
69
70       The HTCondor manual has a complete description of COD.
71

OPTIONS

73          -help  Display usage information
74
75          -version
76                 Display version information
77
78          -pool centralmanagerhostname[:portnumber]
79                 Specify  a pool by giving the central manager's host name and
80                 an optional port number
81
82          -name scheddname
83                 Send the command to a machine identified by scheddname
84
85          -addr "<a.b.c.d:port>"
86                 Send the command to a machine located at "<a.b.c.d:port>"
87
88          -lease N
89                 For the request of a new  claim,  automatically  release  the
90                 claim after N seconds.
91
92          request
93                 Create a new COD claim
94
95          release
96                 Relinquish a claim and kill any running job
97
98          activate
99                 Start a job on a given claim
100
101          deactivate
102                 Kill the current job, but keep the claim
103
104          suspend
105                 Suspend the job on a given claim
106
107          renew  Renew the lease to the COD claim
108
109          resume Resume the job on a given claim
110
111          delegate_proxy
112                 Delegate an X509 proxy for the given claim
113

GENERAL REMARKS

EXAMPLES
EXIT STATUS
117       condor_cod  will exit with a status value of 0 (zero) upon success, and
118       it will exit with the value 1 (one) upon failure.
119

AUTHOR
121       HTCondor Team
122

124       1990-2022, Center for High Throughput Computing, Computer Sciences  De‐
125       partment,  University  of  Wisconsin-Madison, Madison, WI, US. Licensed
126       under the Apache License, Version 2.0.
127
128
129
130
1318.8                              Jun 13, 2022                    CONDOR_COD(1)



        

    


            
        

        

            Impressum