condor_ prio changes the priority of one or more jobs in the condor queue. If a cluster_id and a process_id are both specified, condor_ prio attempts to change the priority of the specified process. If a cluster_id is specified without a process_id, condor_ prio attempts to change priority for all processes belonging to the specified cluster. If a username is specified, condor_ prio attempts to change priority of all jobs belonging to that user. If the -a flag is set, condor_ prio attempts to change priority of all jobs in the condor queue. The user must specify a priority adjustment or new priority. If the -p option is specified, the priority of the job(s) are set to the next argument. The user can also adjust the priority by supplying a + or - immediately followed by a digit. The priority of a job can be any integer, with higher numbers corresponding to greater priority. Only the owner of a job or the super user can change the priority for it.
The priority changed by condor_ prio is only compared to the priority of other jobs owned by the same user and submitted from the same machine. See the "Condor Users and Administrators Manual" for further details on Condor's priority scheme.
condor_ prio will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
U.S. Government Rights Restrictions: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable, Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or email@example.com.
See the Condor Version 6.8.3 Manual for additional notices.