1just-man-pages/condor_userpriGoe(n1e)ral Commands Mjaunsuta-lman-pages/condor_userprio(1)
2
3
4
6 condor_userprio Manage user priorities
7
9 condor_userprio [ -pool centralmanagerhostname[:portnumber] ] [ -all ]
10 [ -usage ] [ -setprio username value ] [ -setfactor username value ] [
11 -setaccum username value ] [ -setbegin username value ] [ -setlast
12 username value ] [ -resetusage username ] [ -resetall ] [ -delete user‐
13 name ] [ -getreslist username ] [ -allusers ] [ -activefrom month day
14 year ] [ -l ]
15
17 condor_userprio with no arguments, lists the active users (see below)
18 along with their priorities, in increasing priority order. The -all
19 option can be used to display more detailed information about each
20 user, which includes the following columns:
21
22 Effective Priority
23
24 The effective priority value of the user, which is used to calculate
25 the user's share when allocating resources. A lower value means a
26 higher priority, and the minimum value (highest priority) is 0.5.
27 The effective priority is calculated by multiplying the real prior‐
28 ity by the priority factor.
29
30
31
32 Real Priority
33
34 The value of the real priority of the user. This value follows the
35 user's resource usage.
36
37
38
39 Priority Factor
40
41 The system administrator can set this value for each user, thus con‐
42 trolling a user's effective priority relative to other users. This
43 can be used to create different classes of users.
44
45
46
47 Res Used
48
49 The number of resources currently used (e.g. the number of running
50 jobs for that user).
51
52
53
54 Accumulated Usage
55
56 The accumulated number of resource-hours used by the user since the
57 usage start time.
58
59
60
61 Usage Start Time
62
63 The time since when usage has been recorded for the user. This time
64 is set when a user job runs for the first time. It is reset to the
65 present time when the usage for the user is reset (with the -rese‐
66 tusage or -resetall options).
67
68
69
70 Last Usage Time
71
72 The most recent time a resource usage has been recorded for the
73 user.
74
75
76
77 The -usage option displays the username, accumulated usage, usage start
78 time and last usage time for each user, sorted on accumulated usage.
79
80 The -setprio, -setfactor options are used to change a user's real pri‐
81 ority and priority factor. The -setaccum option sets a user's accumu‐
82 lated usage. The -setbegin, -setlast options are used to change a
83 user's begin usage time and last usage time. The -setaccum option sets
84 a user's accumulated usage. The -resetusage and -resetall options are
85 used to reset the accumulated usage for users. The usage start time is
86 set to the current time when the accumulated usage is reset. These
87 options require administrator privileges.
88
89 By default only users for whom usage was recorded in the last 24 hours
90 or whose priority is greater than the minimum are listed. The -active‐
91 from and -allusers options can be used to display users who had some
92 usage since a specified date, or ever. The summary line for last usage
93 time will show this date.
94
95 The -getreslist option is used to display the resources currently used
96 by a user. The output includes the start time (the time the resource
97 was allocated to the user), and the match time (how long has the
98 resource been allocated to the user).
99
100 Note that when specifying user names on the command line, the name must
101 include the UID domain (e.g. user@uid-domain - exactly the same way
102 user names are listed by the userprio command).
103
104 The -pool option can be used to contact a different central-manager
105 instead of the local one (the default).
106
107 For security purposes (authentication and authorization), this command
108 requires an administrator's level of access. See section on page for
109 further explanation.
110
112 -pool centralmanagerhostname[:portnumber]
113
114 Contact specified centralmanagerhostname with an optional port num‐
115 ber instead of the local central manager. This can be used to check
116 other pools. NOTE: The host name (and optionally port) specified
117 refer to the host name (and port) of the condor_negotiator to query
118 for user priorities. This is slightly different than most Condor
119 tools that support -pool, which expect the host name (and optionally
120 port) of the condor_collector , instead.
121
122
123
124
125
126 -all
127
128 Display detailed information about each user.
129
130
131
132
133
134 -usage
135
136 Display usage information for each user.
137
138
139
140
141
142 -setprio username value
143
144 Set the real priority of the specified user to the specified value.
145
146
147
148
149
150 -setfactor username value
151
152 Set the priority factor of the specified user to the specified
153 value.
154
155
156
157
158
159 -setaccum username value
160
161 Set the accumulated usage of the specified user to the specified
162 floating point value.
163
164
165
166
167
168 -setbegin username value
169
170 Set the begin usage time of the specified user to the specified
171 value.
172
173
174
175
176
177 -setlast username value
178
179 Set the last usage time of the specified user to the specified
180 value.
181
182
183
184
185
186 -resetusage username
187
188 Reset the accumulated usage of the specified user to zero.
189
190
191
192
193
194 -resetall
195
196 Reset the accumulated usage of all the users to zero.
197
198
199
200
201
202 -delete username
203
204 Remove the specified username from Condor's accounting.
205
206
207
208
209
210 -getreslist username
211
212 Display all the resources currently allocated to the specified user.
213
214
215
216
217
218 -allusers
219
220 Display information for all the users who have some recorded accumu‐
221 lated usage.
222
223
224
225
226
227 -activefrom month day year
228
229 Display information for users who have some recorded accumulated
230 usage since the specified date.
231
232
233
234
235
236 -l
237
238 Show the class-ad which was received from the central-manager in
239 long format.
240
241
242
243
244
246 condor_userprio will exit with a status value of 0 (zero) upon success,
247 and it will exit with the value 1 (one) upon failure.
248
250 Condor Team, University of Wisconsin-Madison
251
253 Copyright (C) 1990-2009 Condor Team, Computer Sciences Department, Uni‐
254 versity of Wisconsin-Madison, Madison, WI. All Rights Reserved.
255 Licensed under the Apache License, Version 2.0.
256
257 See the Condor Version 7.4.2 Manual or http://www.condorpro‐
258 ject.org/licensefor additional notices. condor-admin@cs.wisc.edu
259
260
261
262 date just-man-pages/condor_userprio(1)