1condor_userprio(1) General Commands Manual condor_userprio(1)
2
3
4
6 condor_userprioManage user priorities
7
9 condor_userprio-help
10
11 condor_userprio[-name negotiatorname] [-pool centralmanagerhost‐
12 name[:portnumber]] [Edit option] | [Display options] [-inputfile file‐
13 name]
14
16 condor_userprioeither modifies priority-related information or displays
17 priority-related information. Displayed information comes from the
18 accountant log, where the condor_negotiatordaemon stores historical
19 usage information in the file at $(SPOOL)/Accountantnew.log. Which
20 fields are displayed changes based on command line arguments. con‐
21 dor_userpriowith no arguments, lists the active users along with their
22 priorities, in increasing priority order. The -alloption can be used to
23 display more detailed information about each user, resulting in a
24 rather wide display, and includes the following columns:
25
26 Effective Priority
27
28 The effective priority value of the user, which is used to calculate
29 the user's share when allocating resources. A lower value means a
30 higher priority, and the minimum value (highest priority) is 0.5.
31 The effective priority is calculated by multiplying the real prior‐
32 ity by the priority factor.
33
34
35
36 Real Priority
37
38 The value of the real priority of the user. This value follows the
39 user's resource usage.
40
41
42
43 Priority Factor
44
45 The system administrator can set this value for each user, thus con‐
46 trolling a user's effective priority relative to other users. This
47 can be used to create different classes of users.
48
49
50
51 Res Used
52
53 The number of resources currently used.
54
55
56
57 Accumulated Usage
58
59 The accumulated number of resource-hours used by the user since the
60 usage start time.
61
62
63
64 Usage Start Time
65
66 The time since when usage has been recorded for the user. This time
67 is set when a user job runs for the first time. It is reset to the
68 present time when the usage for the user is reset.
69
70
71
72 Last Usage Time
73
74 The most recent time a resource usage has been recorded for the
75 user.
76
77
78
79 By default only users for whom usage was recorded in the last 24 hours,
80 or whose priority is greater than the minimum are listed.
81
82 The -pooloption can be used to contact a different central manager than
83 the local one (the default).
84
85 For security purposes of authentication and authorization, specifying
86 an Edit Option requires the ADMINISTRATOR level of access.
87
89 -help
90
91 Display usage information and exit.
92
93
94
95
96
97 -name negotiatorname
98
99 When querying ads from the condor_collector, only retrieve ads that
100 came from the negotiator with the given name.
101
102
103
104
105
106 -pool centralmanagerhostname[:portnumber]
107
108 Contact the specified centralmanagerhostnamewith an optional port
109 number, instead of the local central manager. This can be used to
110 check other pools. NOTE: The host name (and optional port) specified
111 refer to the host name (and port) of the condor_negotiatorto query
112 for user priorities. This is slightly different than most HTCondor
113 tools that support a -pooloption, and instead expect the host name
114 (and port) of the condor_collector.
115
116
117
118
119
120 -inputfile filename
121
122 Introduced for debugging purposes, read priority information from
123 filename. The contents of filenameare expected to be the same as
124 captured output from running a condor_userprio -longcommand.
125
126
127
128
129
130 -delete username
131
132 (Edit option) Remove the specified usernamefrom HTCondor's account‐
133 ing.
134
135
136
137
138
139 -resetall
140
141 (Edit option) Reset the accumulated usage of all the users to zero.
142
143
144
145
146
147 -resetusage username
148
149 (Edit option) Reset the accumulated usage of the user specified by
150 usernameto zero.
151
152
153
154
155
156 -setaccum username value
157
158 (Edit option) Set the accumulated usage of the user specified by
159 usernameto the specified floating point value.
160
161
162
163
164
165 -setbegin username value
166
167 (Edit option) Set the begin usage time of the user specified by
168 usernameto the specified value.
169
170
171
172
173
174 -setfactor username value
175
176 (Edit option) Set the priority factor of the user specified by user‐
177 nameto the specified value.
178
179
180
181
182
183 -setlast username value
184
185 (Edit option) Set the last usage time of the user specified by user‐
186 nameto the specified value.
187
188
189
190
191
192 -setprio username value
193
194 (Edit option) Set the real priority of the user specified by user‐
195 nameto the specified value.
196
197
198
199
200
201 -activefrom month day year
202
203 (Display option) Display information for users who have some
204 recorded accumulated usage since the specified date.
205
206
207
208
209
210 -all
211
212 (Display option) Display all available fields about each group or
213 user.
214
215
216
217
218
219 -allusers
220
221 (Display option) Display information for all the users who have some
222 recorded accumulated usage.
223
224
225
226
227
228 -negotiator
229
230 (Display option) Force the query to come from the negotiator instead
231 of the collector.
232
233
234
235
236
237 -autoformat[:jlhVr,tng] attr1 [attr2 ...]or -af[:jlhVr,tng] attr1
238 [attr2 ...]
239
240 (Display option) Display attribute(s) or expression(s) formatted in
241 a default way according to attribute types. This option takes an
242 arbitrary number of attribute names as arguments, and prints out
243 their values, with a space between each value and a newline charac‐
244 ter after the last value. It is like the -formatoption without for‐
245 mat strings.
246
247 It is assumed that no attribute names begin with a dash character,
248 so that the next word that begins with dash is the start of the next
249 option. The autoformatoption may be followed by a colon character
250 and formatting qualifiers to deviate the output formatting from the
251 default:
252
253 jprint the job ID as the first field,
254
255 llabel each field,
256
257 hprint column headings before the first line of output,
258
259 Vuse %V rather than %v for formatting (string values are quoted),
260
261 rprint "raw", or unevaluated values,
262
263 ,add a comma character after each field,
264
265 tadd a tab character before each field instead of the default space
266 character,
267
268 nadd a newline character after each field,
269
270 gadd a newline character between ClassAds, and suppress spaces
271 before each field.
272
273 Use -af:hto get tabular values with headings.
274
275 Use -af:lrngto get -long equivalent format.
276
277 The newline and comma characters may notbe used together. The land
278 hcharacters may notbe used together.
279
280
281
282
283
284 -constraint <expr>
285
286 (Display option) To be used in conjunction with the -long-modularor
287 the -autoformatoptions. Displays users and groups that match the
288 <expr>.
289
290
291
292
293
294 -debug[:<opts>]
295
296 (Display option) Without :<opts>specified, use configured debug
297 level to send debugging output to stderr. With :<opts>specified,
298 these options are debug levels that override any configured debug
299 levels for this command's execution to send debugging output to
300 stderr.
301
302
303
304
305
306 -flat
307
308 (Display option) Display information such that users within hierar‐
309 chical groups are notlisted with their group.
310
311
312
313
314
315 -getreslist username
316
317 (Display option) Display all the resources currently allocated to
318 the user specified by username.
319
320
321
322
323
324 -grouporder
325
326 (Display option) Display submitter information with accounting group
327 entries at the top of the list, and in breadth-first order within
328 the group hierarchy tree.
329
330
331
332
333
334 -grouprollup
335
336 (Display option) For hierarchical groups, the display shows sums as
337 computed for groups, and these sums include sub groups.
338
339
340
341
342
343 -hierarchical
344
345 (Display option) Display information such that users within hierar‐
346 chical groups are listed with their group.
347
348
349
350
351
352 -legacy
353
354 (Display option) For use with the -longoption, displays attribute
355 names and values as a single ClassAd.
356
357
358
359
360
361 -long
362
363 (Display option) A verbose output which displays entire ClassAds.
364
365
366
367
368
369 -modular
370
371 (Display option) Modifies the display when using the -longoption,
372 such that attribute names and values are shown as distinct ClassAds.
373
374
375
376
377
378 -most
379
380 (Display option) Display fields considered to be the most useful.
381 This is the default set of fields displayed.
382
383
384
385
386
387 -priority
388
389 (Display option) Display fields with user priority information.
390
391
392
393
394
395 -quotas
396
397 (Display option) Display fields relevant to hierarchical group quo‐
398 tas.
399
400
401
402
403
404 -usage
405
406 (Display option) Display usage information for each group or user.
407
408
409
410
411
413 Example 1Since the output varies due to command line arguments, here is
414 an example of the default output for a pool that does not use Hierar‐
415 chical Group Quotas. This default output is the same as given with the
416 -mostDisplay option.
417
418 Last Priority Update: 1/19 13:14
419 Effective Priority Res Total Usage Time
420 Since
421 User Name Priority Factor In Use (wghted-hrs) Last
422 Usage
423 ---------------------- ------------ --------- ------ ------------
424 ----------
425 www-cndr@cs.wisc.edu 0.56 1.00 0 591998.44
426 0+16:30
427 joey@cs.wisc.edu 1.00 1.00 1 990.15 <now>
428 suzy@cs.wisc.edu 1.53 1.00 0 261.78
429 0+09:31
430 leon@cs.wisc.edu 1.63 1.00 2 12597.82 <now>
431 raj@cs.wisc.edu 3.34 1.00 0 8049.48
432 0+01:39
433 jose@cs.wisc.edu 3.62 1.00 4 58137.63 <now>
434 betsy@cs.wisc.edu 13.47 1.00 0 1475.31
435 0+22:46
436 petra@cs.wisc.edu 266.02 500.00 1 288082.03 <now>
437 carmen@cs.wisc.edu 329.87 10.00 634 2685305.25 <now>
438 carlos@cs.wisc.edu 687.36 10.00 0 76555.13
439 0+14:31
440 ali@proj1.wisc.edu 5000.00 10000.00 0 1315.56
441 0+03:33
442 apu@nnland.edu 5000.00 10000.00 0 482.63
443 0+09:56
444 pop@proj1.wisc.edu 26688.11 10000.00 1 49560.88 <now>
445 franz@cs.wisc.edu 29352.06 500.00 109 600277.88 <now>
446 martha@nnland.edu 58030.94 10000.00 0 48212.79
447 0+12:32
448 izzi@nnland.edu 62106.40 10000.00 0 6569.75
449 0+02:26
450 marta@cs.wisc.edu 62577.84 500.00 29 193706.30 <now>
451 kris@proj1.wisc.edu 100597.94 10000.00 0 20814.24
452 0+04:26
453 boss@proj1.wisc.edu 318229.25 10000.00 3 324680.47 <now>
454 ---------------------- ------------ --------- ------ ------------
455 ----------
456 Number of users: 19 784 4969073.00
457 0+23:59
458
459 Example 2This is an example of the default output for a pool that uses
460 hierarchical groups, and the groups accept surplus. This leads to a
461 very wide display.
462
463 % condor_userprio -pool crane.cs.wisc.edu -allusers
464 Last Priority Update: 1/19 13:18
465 Group Config Use Effective
466 Priority Res Total Usage Time Since
467 User Name Quota Surplus Priority
468 Factor In Use (wghted-hrs) Last Usage
469 ------------------------------------ --------- ------- ------------
470 --------- ------ ------------ ----------
471 <none> 0.00 yes
472 1.00 0 6.78 9+03:52
473 johnsm@crane.cs.wisc.edu 0.50
474 1.00 0 6.62 9+19:42
475 John.Smith@crane.cs.wisc.edu 0.50
476 1.00 0 0.02 9+03:52
477 Sedge@crane.cs.wisc.edu 0.50
478 1.00 0 0.05 13+03:03
479 Duck@crane.cs.wisc.edu 0.50
480 1.00 0 0.02 31+00:28
481 other@crane.cs.wisc.edu 0.50
482 1.00 0 0.04 16+03:42
483 Duck 2.00 no
484 1.00 0 0.02 13+02:57
485 goose@crane.cs.wisc.edu 0.50
486 1.00 0 0.02 13+02:57
487 Sedge 4.00 no
488 1.00 0 0.17 9+03:07
489 johnsm@crane.cs.wisc.edu 0.50
490 1.00 0 0.13 9+03:08
491 Half@crane.cs.wisc.edu 0.50
492 1.00 0 0.02 31+00:02
493 John.Smith@crane.cs.wisc.edu 0.50
494 1.00 0 0.05 9+03:07
495 other@crane.cs.wisc.edu 0.50
496 1.00 0 0.01 28+19:34
497 ------------------------------------ --------- ------- ------------
498 --------- ------ ------------ ----------
499 Number of users: 10 ByQuota
500 0 6.97
501
503 condor_userpriowill exit with a status value of 0 (zero) upon success,
504 and it will exit with the value 1 (one) upon failure.
505
507 Center for High Throughput Computing, University of Wisconsin-Madison
508
510 Copyright (C) 1990-2019 Center for High Throughput Computing, Computer
511 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
512 Rights Reserved. Licensed under the Apache License, Version 2.0.
513
514
515
516 date condor_userprio(1)