1CONDOR_PRIO(1)                  HTCondor Manual                 CONDOR_PRIO(1)
2
3
4

NAME

6       condor_prio - HTCondor Manual
7
8       change priority of jobs in the HTCondor queue
9
10

SYNOPSIS

12       condor_prio -p priority | + ** *value* | **- value [-n schedd_name] **
13
14       condor_prio  -p priority | + ** *value* | **- value [-pool pool_name -n
15       schedd_name ]**
16

DESCRIPTION

18       condor_prio changes the priority of one or more jobs  in  the  HTCondor
19       queue.  If  the  job  identification  is given by cluster.process, con‐
20       dor_prio attempts to change the priority of the  single  job  with  job
21       ClassAd  attributes ClusterId and ProcId. If described by cluster, con‐
22       dor_prio attempts to change the priority  of  all  processes  with  the
23       given  ClusterId  job ClassAd attribute. If username is specified, con‐
24       dor_prio attempts to change priority of  all  jobs  belonging  to  that
25       user.  For  -a,  condor_prio attempts to change priority of all jobs in
26       the queue.
27
28       The user must set a new priority with the -p option, or specify a  pri‐
29       ority adjustment. The priority of a job can be any integer, with higher
30       numbers corresponding to greater priority. For adjustment of  the  cur‐
31       rent  priority, + ** *value* increases the priority by the amount given
32       with *value*. **- value decreases the priority by the amount given with
33       value.
34
35       Only the owner of a job or the super user can change the priority.
36
37       The  priority changed by condor_prio is only used when comparing to the
38       priority jobs owned by the same user and submitted from  the  same  ma‐
39       chine.
40

OPTIONS

42          -n schedd_name
43                 Change priority of jobs queued at the specified condor_schedd
44                 in the local pool.
45
46          -pool pool_name -n schedd_name
47                 Change priority of jobs queued at the specified condor_schedd
48                 in the specified pool.
49

EXIT STATUS

51       condor_prio will exit with a status value of 0 (zero) upon success, and
52       it will exit with the value 1 (one) upon failure.
53

AUTHOR

55       HTCondor Team
56

58       1990-2022, Center for High Throughput Computing, Computer Sciences  De‐
59       partment,  University  of  Wisconsin-Madison, Madison, WI, US. Licensed
60       under the Apache License, Version 2.0.
61
62
63
64
658.8                              Jan 19, 2022                   CONDOR_PRIO(1)
Impressum