1just-man-pages/condor_cod(1)General Commands Manualjust-man-pages/condor_cod(1)
2
3
4
6 condor_cod manage COD machines and jobs
7
9 condor_cod [ -help -version ]
10
11 condor_cod request [ -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_cod release -id ClaimID [[ -help -version ] [ -debug -timeout N
16 -classad file ] ] [ -fast ]
17
18 condor_cod activate -id ClaimID [[ -help -version ] [ -debug -timeout N
19 -classad file ] ] [ -keyword string -jobad filename -cluster N -proc N
20 -requirements expr ]
21
22 condor_cod deactivate -id ClaimID [[ -help -version ] [ -debug -timeout
23 N -classad file ] ] [ -fast ]
24
25 condor_cod suspend -id ClaimID [[ -help -version ] [ -debug -timeout N
26 -classad file ] ]
27
28 condor_cod renew -id ClaimID [[ -help -version ] [ -debug -timeout N
29 -classad file ] ]
30
31 condor_cod resume -id ClaimID [[ -help -version ] [ -debug -timeout N
32 -classad file ] ]
33
34 condor_cod delegate_proxy -id ClaimID [[ -help -version ] [ -debug
35 -timeout N -classad file ] ] [ -x509proxy ProxyFile ]
36
38 condor_cod issues commands that manage and use COD claims on machines,
39 given proper authorization.
40
41 Instead of specifying an argument of request , release , activate ,
42 deactivate , suspend , renew , or resume , the user may invoke the con‐
43 dor_cod tool by appending an underscore followed by one of these argu‐
44 ments. As 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_cod executable. For example on a Unix machine:
52
53 ln condor_cod_request condor_cod
54
55 The request argument gives a claim ID, and the other commands ( release
56 , activate , deactivate , suspend , and resume ) use the claim ID. The
57 claim ID is given as the last line of output for a request , and the
58 output appears of the form:
59
60 ID of new claim is: "<a.b.c.d:portnumber>#x#y"
61
62 An actual example of this line of output is
63
64 ID of new claim is: "<128.105.121.21:49973>#1073352104#4"
65
66 Also see section for more a complete description of COD.
67
69 -help
70
71 Display usage information
72
73
74
75 -version
76
77 Display version information
78
79
80
81 -pool centralmanagerhostname[:portnumber]
82
83 Specify a pool by giving the central manager's host name and an
84 optional port number
85
86
87
88 -name scheddname
89
90 Send the command to a machine identified by scheddname
91
92
93
94 -addr <a.b.c.d:port>
95
96 Send the command to a machine located at <a.b.c.d:port>
97
98
99
100 -lease N
101
102 For the request of a new claim, automatically release the claim
103 after N seconds.
104
105
106
107 request
108
109 Create a new COD claim
110
111
112
113 release
114
115 Relinquish a claim and kill any running job
116
117
118
119 activate
120
121 Start a job on a given claim
122
123
124
125 deactivate
126
127 Kill the current job, but keep the claim
128
129
130
131 suspend
132
133 Suspend the job on a given claim
134
135
136
137 renew
138
139 Renew the lease to the COD claim
140
141
142
143 resume
144
145 Resume the job on a given claim
146
147
148
149 delegate_proxy
150
151 Delegate an X509 proxy for the given claim
152
153
154
158 condor_cod will exit with a status value of 0 (zero) upon success, and
159 it will exit with the value 1 (one) upon failure.
160
162 Condor Team, University of Wisconsin-Madison
163
165 Copyright (C) 1990-2009 Condor Team, Computer Sciences Department, Uni‐
166 versity of Wisconsin-Madison, Madison, WI. All Rights Reserved.
167 Licensed under the Apache License, Version 2.0.
168
169 See the Condor Version 7.4.2 Manual or http://www.condorpro‐
170 ject.org/licensefor additional notices. condor-admin@cs.wisc.edu
171
172
173
174 date just-man-pages/condor_cod(1)