1condor_cod(1)               General Commands Manual              condor_cod(1)
2
3
4

Name

6       condor_codmanage COD machines and jobs
7

Synopsis

9       condor_cod[-help | -version]
10
11       condor_codrequest[   -pool  centralmanagerhostname[:portnumber]|  -name
12       scheddname] | [-addr "<a.b.c.d:port>"] [ [-help | -version] | [-debug |
13       -timeout N | -classad file] ] [-requirements expr] [-lease N]
14
15       condor_codrelease-id ClaimID[ [-help | -version] | [-debug | -timeout N
16       | -classad file] ] [-fast]
17
18       condor_codactivate-id ClaimID[ [-help | -version] | [-debug |  -timeout
19       N  | -classad file] ] [-keyword string | -jobad filename | -cluster N |
20       -proc N | -requirements expr]
21
22       condor_coddeactivate-id ClaimID[ [-help | -version] | [-debug |  -time‐
23       out N | -classad file] ] [-fast]
24
25       condor_codsuspend-id ClaimID[ [-help | -version] | [-debug | -timeout N
26       | -classad file] ]
27
28       condor_codrenew-id ClaimID[ [-help | -version] | [-debug | -timeout N |
29       -classad file] ]
30
31       condor_codresume-id  ClaimID[ [-help | -version] | [-debug | -timeout N
32       | -classad file] ]
33
34       condor_coddelegate_proxy-id ClaimID[ [-help |  -version]  |  [-debug  |
35       -timeout N | -classad file] ] [-x509proxy ProxyFile]
36

Description

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

Options

68       -help
69
70          Display usage information
71
72
73
74       -version
75
76          Display version information
77
78
79
80       -pool centralmanagerhostname[:portnumber]
81
82          Specify a pool by giving the central  manager's  host  name  and  an
83          optional port number
84
85
86
87       -name scheddname
88
89          Send the command to a machine identified by scheddname
90
91
92
93       -addr <a.b.c.d:port>
94
95          Send the command to a machine located at "<a.b.c.d:port>"
96
97
98
99       -lease N
100
101          For the requestof a new claim, automatically release the claim after
102          Nseconds.
103
104
105
106       request
107
108          Create a new COD claim
109
110
111
112       release
113
114          Relinquish a claim and kill any running job
115
116
117
118       activate
119
120          Start a job on a given claim
121
122
123
124       deactivate
125
126          Kill the current job, but keep the claim
127
128
129
130       suspend
131
132          Suspend the job on a given claim
133
134
135
136       renew
137
138          Renew the lease to the COD claim
139
140
141
142       resume
143
144          Resume the job on a given claim
145
146
147
148       delegate_proxy
149
150          Delegate an X509 proxy for the given claim
151
152
153

General Remarks

Examples
Exit Status
157       condor_codwill exit with a status value of 0 (zero) upon  success,  and
158       it will exit with the value 1 (one) upon failure.
159

Author
161       Center   for   High   Throughput   Computing,   University  of  Wiscon‐
162       sin&ndash;Madison
163

165       Copyright © 1990-2019 Center for High  Throughput  Computing,  Computer
166       Sciences  Department, University of Wisconsin-Madison, Madison, WI. All
167       Rights Reserved. Licensed under the Apache License, Version 2.0.
168
169
170
171                                     date                        condor_cod(1)



        

    


            
        

        

            Impressum