CONDOR_USERPRIO(1)

🌸 condor_userprio β€” the HTCondor Manual, bestie edition πŸ’…

okay so picture this: it's CONDOR_USERPRIO(1), straight out of the HTCondor Manual, and it's here to let you poke at submitter priorities. yes queen. let's go 🫢


✨ NAME ✨

condor_userprio β€” manage submitter priorities πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

condor_userprio [-help]

condor_userprio [-name negotiatorname] [-inputfile filename] [-pool hostname[:port]] [Edit Option | Display Options [submitter]]

🌈 DESCRIPTION 🌈

So basically, condor_userprio is your girl for modifying or displaying priority info for submitters and/or groups, pulling straight from HTCondor's accounting. And by default? It only shows you the active submitters β€” meaning the ones whose usage got recorded in the last 24 hours. lowkey efficient. ✨

NOTE: 🌸 For the purposes of accounting and fair share, HTCondor "charges" usage to a submitter. A submitter, by default, is the same as the operating system user. This means one user of HTCondor, such as Taylor, may have multiple submitter accounts on different Access Points β€” i.e. taylor@ap1.chtc.wisc.edu and taylor@ap2.chtc.wisc.edu.

it's giving "one girly, many accounts" and honestly? iconic.


πŸ’… OPTIONS πŸ’…

🌟 General 🌟

  • -debug[:level] β€” sends debugging info to stderr, based on whatever the config variable TOOL_DEBUG says. you can toss in optional debug levels if you're feeling extra. πŸ”₯
  • -help β€” shows you the tool usage info. the "help me help you" moment, periodt.
  • -inputfile filename β€” reads priority information from filename. πŸ“‚
  • -name negotiatorname β€” sends the command to a machine identified by negotiatorname. πŸŽ€
  • -pool hostname[:port] β€” specify a pool by handing over the central manager's host name plus an optional port number. 🌐

🧚 Edit Options 🧚

  • -delete submitter β€” removes the specified submitter from HTCondor's accounting. bye boo πŸ‘‹
  • -resetall β€” resets the accumulated usage of all the submitters to zero. clean slate energy.
  • -resetusage submitter β€” resets the accumulated usage of the submitter you name to zero.
  • -setaccum submitter value β€” sets the accumulated usage of the specified submitter to the floating point value you give it.
  • -setbegin submitter value β€” sets the begin usage time of the specified submitter to value.
  • -setlast submitter value β€” sets the last usage time of the specified submitter to value.
  • -setfactor submitter value β€” sets the priority factor of the specified submitter to value. and when you pair it with -duration, the priority factor becomes a temporary lease: at the next negotiation cycle on or after seconds have elapsed, the priority factor is automatically restored to its prior value. the lease state is persistent across a condor_negotiator restart. ⚠️ and it is an error to set a lease while one is already in effect for the same submitter β€” cancel the existing lease first with -cancelfactorlease.
  • -setprio submitter value β€” sets the real priority of the specified submitter to value.
  • -setceiling submitter value β€” sets the ceiling for the specified submitter to value. where value is the sum of the SlotWeight of all running jobs (See SLOT_WEIGHT). setting the ceiling to -1 clears any previously set ceiling, and sets the effective ceiling to unlimited. ♾️ when combined with -duration, the ceiling becomes a temporary lease: at the next negotiation cycle on or after seconds have elapsed, the ceiling is automatically restored to its prior value. lease state is persistent, so it survives a condor_negotiator restart. and again β€” it is an error to set a lease while one is already in effect for the same submitter; cancel the existing lease first with -cancelceilinglease.
  • -duration seconds β€” only valid with -setceiling, -setfloor, or -setfactor. makes the corresponding value a lease that expires after seconds seconds, at which point the prior value is restored. ⏳
  • -cancelceilinglease submitter β€” cancels an in-effect ceiling lease for submitter, immediately restoring the ceiling value that was in effect before the lease was set. it is an error if no lease is in effect. 🚫
  • -cancelfloorlease submitter β€” cancels an in-effect floor lease for submitter, immediately restoring the floor value that was in effect before the lease was set. it is an error if no lease is in effect. 🚫
  • -cancelfactorlease submitter β€” cancels an in-effect priority-factor lease for submitter, immediately restoring the priority factor that was in effect before the lease was set. it is an error if no lease is in effect. 🚫
  • -setfloor submitter value β€” sets the floor for the specified submitter to value. where value is the sum of the SlotWeight of all running jobs (See SLOT_WEIGHT). setting the floor to 0 clears any previously set floor. when combined with -duration, the floor becomes a temporary lease: at the next negotiation cycle on or after seconds have elapsed, the floor is automatically restored to its prior value. lease state is persistent across a condor_negotiator restart. and yep, you guessed it β€” it is an error to set a lease while one is already in effect for the same submitter; cancel the existing lease first with -cancelfloorlease.

πŸŽ€ Display Options πŸŽ€

  • -activefrom month day year β€” displays info for submitters who have some recorded accumulated usage since the date you specify. πŸ“…
  • -all β€” displays all available fields about each group or submitters (active). the "give me everything" option.
  • -allusers β€” displays information for all the submitters (active and inactive) who have some recorded accumulated usage. everyone's invited to the party πŸŽ‰
  • -collector β€” forces the query to come from the collector.
  • -negotiator β€” forces the query to come from the negotiator instead of the collector.
  • -af / -autoformat[:jlhVr,tng] Attribute [Attribute ...] β€” displays attribute(s) or expression(s) formatted in a default way, depending on the type of each Attribute you list after the option. it's assumed that no Attributes begin with a dash character, so the next word that begins with a dash is treated as another option. you can follow this option with a colon and formatting qualifiers to deviate the output formatting from the default:
    • j β€” prints the ClassAds associated JobID as the first field.
    • l β€” labels each field.
    • h β€” prints column headings before the first line of output.
    • V β€” uses %V rather than %v for formatting (string values are quoted).
    • r β€” prints "raw", or unevaluated values.
    • , β€” adds a comma character after each field.
    • t β€” adds a tab character before each field instead of the default space character.
    • n β€” adds a newline character after each field.
    • g β€” adds a newline character between ClassAds, and suppresses spaces before each field.
WARNING: ⚠️ The n and , qualifiers may not be used together. Also, the l and h qualifiers may not be used together.
  • -constraint expr β€” displays submitters and groups that satisfy the expression. 🧐
  • -flat β€” displays information such that submitters within hierarchical groups are not listed with their group.
  • -groupid β€” displays group ID.
  • -getreslist submitter β€” displays all the resources currently allocated to the submitter you specify. πŸ–₯️
  • -grouporder β€” displays submitter information with accounting group entries at the top of the list, and in breadth-first order within the group hierarchy tree. 🌳
  • -grouprollup β€” for hierarchical groups, the display shows sums as computed for groups, and these sums include sub groups.
  • -hierarchical β€” displays information such that submitters within hierarchical groups are listed with their group.
  • -legacy β€” for use with the -long option, displays attribute names and values as a single ClassAd.
  • -long β€” displays ClassAds in long format.
  • -modular β€” modifies the display when using the -long option, such that attribute names and values are shown as distinct ClassAds.
  • -order β€” displays group order.
  • -priority β€” displays fields with submitter priority information.
  • -most β€” displays fields considered to be the most useful. this is the default set of fields displayed. ✨
  • -quotas β€” displays fields relevant to hierarchical group quotas.
  • -sortkey β€” displays group sort key.
  • -surplus β€” displays usage surplus.
  • -usage β€” displays usage information for each group or submitter.
  • submitter β€” displays information only for the specified submitter. 🎯

πŸ’… GENERAL REMARKS πŸ’…

okay so bestie, here's what the default tool output is gonna show you for each active submitter. Every field, every vibe, no skipping ✨

  • Effective Priority β€” the effective priority value of the submitter, which is used to calculate the submitter's share when allocating resources. A lower value means a higher priority (yes fr, it's backwards like that 😭), and the minimum value (highest priority) is 0.5. It's calculated by multiplying the real priority by the priority factor.
  • Priority Factor β€” the system administrator can set this value for each submitter, which controls a submitter's effective priority relative to other submitters. This can be used to create different classes of submitters πŸ‘‘
  • Weighted In Use β€” the number of resources currently used.
  • Total Usage (Weighted hours) β€” the accumulated number of resource-hours used by the submitter since the usage start time.
  • Time Since Last Usage β€” elapsed time since the specific submitter last had claimed resources.
  • Submitter Floor β€” the minimum guaranteed number of CPU cores assigned to the specific submitter.
  • Submitter Ceiling β€” maximum number of CPU cores assigned to the specific submitter.

when you run it with the -all option, you get these bonus columns too πŸŽ€

  • Real Priority β€” the value of the real priority of the submitter. This value follows the submitter's resource usage.
  • Usage Start Time β€” the time since when usage has been recorded for the submitter. This time is set when a submitter job runs for the first time. It gets reset to the present time when the usage for the submitter is reset.
  • Last Usage Time β€” the most recent time a resource usage has been recorded for the submitter.

πŸ”’ for security purposes of authentication and authorization, specifying an Edit Option requires the ADMINISTRATOR level of access. no sneaky edits unless you've got the clearance, bestie πŸ’…

🌈 EXIT STATUS 🌈

  • 0 β€” success, we ate πŸ’–
  • 1 β€” failure has occurred 😭

✨ EXAMPLES ✨

display default info about active submitters

$ condor_userprio

display all the info about active submitters

$ condor_userprio -all

display default info for active submitters Bill and Ted associated with Access Point excellent.host.machine

$ condor_userprio bill@excellent.host.machine ted@excellent.host.machine

display default info for every submitter

$ condor_userprio -allusers

display usage info for all active submitters

$ condor_userprio -usage

remove submitter taylor@ap2.chtc.wisc.edu from HTCondor's accounting (bye bestie 🫢)

$ condor_userprio -delete taylor@ap2.chtc.wisc.edu

reset accumulated usages for all submitters to zero

$ condor_userprio -resetall

reset accumulated usage for submitter jfk@white.house.gov to zero

$ condor_userprio -resetusage jfk@white.house.gov

set submitter frodo@mount.doom.mordor accumulated usage to 6.0

$ condor_userprio -setaccum frodo@mount.doom.mordor 6.0

set submitter taylor@ap1.cthc.wisc.edu priority to 100

$ condor_userprio -setprio taylor@ap1.cthc.wisc.edu 100

set submitter taylor@ap1.cthc.wisc.edu usage ceiling to 50

$ condor_userprio -setceiling taylor@ap1.cthc.wisc.edu 50

set submitter taylor@ap1.cthc.wisc.edu usage floor floor to 5

$ condor_userprio -setfloor taylor@ap1.cthc.wisc.edu 5

πŸ‘€ SEE ALSO πŸ‘€

None. literally nothing else to link, that's the whole squad πŸ’€

πŸ¦‹ AVAILABILITY πŸ¦‹

Linux, MacOS, Windows β€” it's giving multi-platform icon behavior ✨

πŸ’– AUTHOR πŸ’–

HTCondor Team

1990-2026, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.


and that's the whole page bestie!! this was the CONDOR_USERPRIO(1) manual, dated Oct 16, 2026, from the HTCondor crew πŸ’… go forth and prioritize, you've totally got this πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from