1just-man-pages/condor_advertiGseen(e1r)al CommandsjMuasntu-amlan-pages/condor_advertise(1)
2
6 condor_advertise Send a ClassAd to the condor_collector daemon
7
9 condor_advertise [ -help -version ]
10 condor_advertise [ -pool centralmanagerhostname[:portname] ] [ -debug ]
12 [ -tcp ] [ -udp ] [ -multiple ] update-command [ classad-filename ]
13
15 condor_advertise sends one or more ClassAds to the condor_collector
16 daemon on the central manager machine. The required argument update-
17 command says what daemon type's ClassAd is to be updated. The optional
18 argument classad-filename is the file from which the ClassAd(s) should
19 be read. If classad-filename is omitted or is the dash character ('-'),
20 then the ClassAd(s) are read from standard input.
21 When -multiple is specified, multiple ClassAds may be published. Pub‐
23 lishing many ClassAds in a single invocation of condor_advertise is
24 more efficient than invoking condor_advertise once per ClassAd. The
25 ClassAds are expected to be separated by one or more blank lines. When
26 -multiple is not specified, blank lines are ignored (for backward com‐
27 patibility). It is best not to rely on blank lines being ignored, as
28 this may change in the future.
29 The update-command may be one of the following strings:
31 UPDATE_STARTD_AD
33 UPDATE_SCHEDD_AD
39 UPDATE_MASTER_AD
45 UPDATE_GATEWAY_AD
51 UPDATE_CKPT_SRVR_AD
57 UPDATE_NEGOTIATOR_AD
63 UPDATE_HAD_AD
69 UPDATE_AD_GENERIC
75 UPDATE_SUBMITTOR_AD
81 UPDATE_COLLECTOR_AD
87 UPDATE_LICENSE_AD
93 UPDATE_STORAGE_AD
99 condor_advertise can also be used to invalidate and delete ClassAds
105 currently held by the condor_collector daemon. In this case the update-
106 command will be one of the following strings:
107 INVALIDATE_STARTD_ADS
109 INVALIDATE_SCHEDD_ADS
115 INVALIDATE_MASTER_ADS
121 INVALIDATE_GATEWAY_ADS
127 INVALIDATE_CKPT_SRVR_ADS
133 INVALIDATE_NEGOTIATOR_ADS
139 INVALIDATE_HAD_ADS
145 INVALIDATE_ADS_GENERIC
151 INVALIDATE_SUBMITTOR_ADS
157 INVALIDATE_COLLECTOR_ADS
163 INVALIDATE_LICENSE_ADS
169 INVALIDATE_STORAGE_ADS
175 For any of these INVALIDATE commands, the ClassAd in the required file
181 consists of three entries. The file contents will be similar to:
182 MyType = "Query"
184 TargetType = "Machine"
185 Requirements = Name == "condor.example.com"
186 The definition for MyType is always Query . TargetType is set to the
188 MyType of the ad to be deleted. This MyType is DaemonMaster for the
189 condor_master ClassAd, Machine for the condor_startd ClassAd, Sched‐
190 uler for the condor_schedd ClassAd, and Negotiator for the con‐
191 dor_negotiator ClassAd. Requirements is an expression evaluated within
192 the context of ads of TargetType . When Requirements evaluates to
193 True , the matching ad is invalidated. A full example is given below.
194
196 -help
197 Display usage information
199 -version
203 Display version information
205 -debug
209 Print debugging information as the command executes.
211 -multiple
215 Send more than one ClassAd, where the boundary between ClassAds is
217 one or more blank lines.
218 -pool centralmanagerhostname[:portname]
222 Specify a pool by giving the central manager's host name and an
224 optional port number. The default is the COLLECTOR_HOST specified
225 in the configuration file.
226 -tcp
230 Use TCP for communication. Used by default if UPDATE_COLLEC‐
232 TOR_WITH_TCP is true.
233 -udp
237 Use UDP for communication.
239
243 The job and machine ClassAds are regularly updated. Therefore, the
244 result of condor_advertise is likely to be overwritten in a very short
245 time. It is unlikely that either HTCondor users (those who submit jobs)
246 or administrators will ever have a use for this command. If it is
247 desired to update or set a ClassAd attribute, the condor_config_val
248 command is the proper command to use.
249 Attributes are defined in Appendix A of the HTCondor manual.
251 For those administrators who do need condor_advertise , the following
253 attributes may be included:
254 DaemonStartTime
256 UpdateSequenceNumber
262 If both of the above are included, the condor_collector will automati‐
268 cally include the following attributes:
269 UpdatesTotal
271 UpdatesLost
277 UpdatesSequenced
283 UpdatesHistory
289 Affected by COLLECTOR_DAEMON_HISTORY_SIZE .
291
295 Assume that a machine called condor.example.com is turned off, yet its
296 condor_startd ClassAd does not expire for another 20 minutes. To avoid
297 this machine being matched, an administrator chooses to delete the
298 machine's condor_startd ClassAd. Create a file (called remove_file in
299 this example) with the three required attributes:
300 MyType = "Query"
302 TargetType = "Machine"
303 Requirements = Name == "condor.example.com"
304 This file is used with the command:
306 % condor_advertise INVALIDATE_STARTD_ADS remove_file
308
310 condor_advertise will exit with a status value of 0 (zero) upon suc‐
311 cess, and it will exit with the value 1 (one) upon failure. Success
312 means that all ClassAds were successfully sent to all condor_collector
313 daemons. When there are multiple ClassAds or multiple condor_collector
314 daemons, it is possible that some but not all publications succeed; in
315 this case, the exit status is 1, indicating failure.
316
318 Center for High Throughput Computing, University of Wisconsin-Madison
319
321 Copyright (C) 1990-2018 Center for High Throughput Computing, Computer
322 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
323 Rights Reserved. Licensed under the Apache License, Version 2.0.
324 date just-man-pages/condor_advertise(1)