QQUOTA(1)

πŸ’… QQUOTA β€” bestie's guide to peeking at your Grid Engine resource quotas ✨

okay so this is qquota(1), a user command from the Grid Engine era, and it literally just shows you the current usage of Grid Engine resource quotas. it's giving "who's hogging what" energy and honestly? iconic. πŸŽ€


✨ SYNTAX ✨

qquota [ -h wc_host|wc_hostgroup,... ] [ -help ] [ -l resource_name,... ]
       [ -u wc_user,... ] [ -P wc_project,... ] [ -pe wc_pe_name,... ]
       [ -q wc_cqueue,... ] [ -xml ]

🌸 DESCRIPTION 🌸

so qquota shows you the current Grid Engine resource quota sets. that's the whole vibe. but here's the tea: it only prints resource quota sets that have a positive usage count or a static limit β€” the deets on that are in OUTPUT FORMAT below, no cap. πŸ’–

the selection options let you filter for specific hosts, cluster queues, projects, parallel environments (pe), resources, or users. pick your fave, filter away. πŸ¦‹

and if you run it with zero options? it just shows you a list of all the resource quota sets for the calling user. cute, simple, main character energy. ✨


πŸ‘‘ OPTIONS πŸ‘‘

  • -h wc_host|wc_hostgroup,... β€” only shows the resource quota sets that match the hosts in the wildcard host or hostgroup list you gave it. the definition of wc_host and wc_hostgroup lives in sge_types(5), go check it out bestie πŸ’œ
  • -help β€” prints a listing of all the options. your little cheat sheet fr fr 🫢
  • -l resource_name,... β€” only shows resource quota sets that match the resources in the resource list you passed. slay πŸ“
  • -u wc_user,... β€” only shows resource quota sets matching the users in the given wildcard user list. wc_user is defined in sge_types(5) ✨
  • -P wc_project,... β€” only shows resource quota sets matching the projects in the given wildcard project list. wc_project? yeah, also in sge_types(5) πŸ’…
  • -pe wc_pe_name,... β€” only shows resource quota sets matching the parallel environments (pe) in the given wildcard pe list. wc_pe_name definition: sge_types(5), as always 🌈
  • -q wc_cqueue,... β€” only shows resource quota sets matching the queues in the given wildcard cluster queue list. wc_cqueue definition is in sge_types(5) too 🧚
  • -xml β€” bestie this one is special, it can be used with all the other options and it switches the output to XML. the schema used is referenced in the XML output itself. and it's printed to stdout. πŸ’–

πŸ“‹ OUTPUT FORMAT πŸ“‹

a line gets printed for every resource quota that has a positive usage count or a static resource. and each line is made of:

  • the resource quota β€” rule set name/rule name, or the number of the rule in the ruleset
  • the limit β€” resource name, plus the number of used and available entities of that resource
  • the effective resource quota set filter

like, that's the whole line. no filler, no fluff. periodt. πŸ’…


🌈 ENVIRONMENT VARIABLES 🌈

  • SGE_ROOT β€” tells you where the Grid Engine standard configuration files live. your home base fr. 🏠
  • SGE_CELL β€” if you set it, it specifies the default Grid Engine cell. to address a Grid Engine cell, qquota uses (in order of precedence):
    1. the name of the cell specified in the environment variable SGE_CELL, if it is set.
    2. the name of the default cell, i.e. default.
  • SGE_DEBUG_LEVEL β€” if you set it, debug info gets written to stderr. and also, the level of detail in which that debug info is generated is defined. so like, you control the vibes of the debugging. πŸ”₯
  • SGE_QMASTER_PORT β€” if you set it, it specifies the tcp port on which sge_qmaster(8) is expected to listen for communication requests. but ngl, most installations will use a services map entry for the service "sge_qmaster" instead to define that port. iykyk 😌

πŸ“ FILES πŸ“

  • <sge_root>/<cell>/common/act_qmaster β€” Grid Engine master host file
  • <sge_root>/<cell>/common/sge_qquota β€” cluster qquota default options
  • $HOME/.sge_qquota β€” user qquota default options

🫢 SEE ALSO 🫢

sge_intro(1), qalter(1), qconf(1), qhold(1), qmod(1), qstat(1), qsub(1), queue_conf(5), sge_execd(8), sge_qmaster(8), sge_shepherd(8).

go read those too bestie, they're all part of the squad πŸ’œ


see sge_intro(1) for a full statement of rights and permissions. that's where the legal lore lives πŸ“œ


okay that's the whole page!! this was SGE 8.1.3pre, dated 2007-07-19, and it's QQUOTA(1) from the Grid Engine User Commands manual. iconic era, iconic tool. bye bestie, go check your quotas πŸ’…βœ¨πŸŽ€