QSELECT(1)

πŸ“¦
version 8.1.9 Β· 2 versions
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– QSELECT(1) β€” Grid Engine User Commands πŸ’–

okay bestie, welcome to qselect from the Grid Engine user commands, no cap. this is the lil cutie that goes and finds queue instances for you. let's get into it πŸ¦‹


✨ NAME ✨

qselect β€” select queues. that's it. that's the whole job. iconic behaviour honestly πŸ’…


πŸŽ€ SYNTAX πŸŽ€

qselect [ -help ] [ -l resource=val,...  ] [ -pe pe_name,...  ] [ -q
wc_queue,...  ] [ -s {r|p|s|z|hu|ho|hs|hj|ha|h}[+] ] [ -U user,...  ]

look at her. all those flags. so much main character energy 🌸


πŸ¦‹ DESCRIPTION πŸ¦‹

so what does qselect actually do, you ask? she prints a list of Grid Engine queue instance names that match whatever selection criteria you gave her in the arguments (they're all described down below, don't worry bb).

lowkey important tea: the output is of limited use, because it's giving queue instances rather than cluster queues or hosts. so like… know that going in. 😭

πŸ’… OPTIONS πŸ’…

  • -help β€” prints a listing of all options. she's helpful like that. a queen. πŸ‘‘
  • -l resource[=value],... β€” defines the resources that the queues should be granting if they wanna show up in the output. matching happens on queues based on non-mutable resource availability information only. translation: load values are always ignored, except for the so-called static load values listed in load_parameters(5). also, consumable utilization gets ignored too, bestie. and if you hit her with multiple -l resource requests, they get concatenated by a logical AND β€” meaning a queue has to offer all the resources to be displayed. all of them. no halfsies. ✨
  • -pe pe_name,... β€” includes queue instances in the output that have at least one of the parallel environments listed in the comma-separated option argument attached to them. just one is enough, she's not demanding 🫢
  • -q wc_queue,... β€” directly specifies the wildcard expression queue list to be included in the output. this option usually is only meaningful in conjunction with another qselect option, so you can extract a subset of queue names from a list given by -q. the description of wc_queue lives in sge_types(5) if you wanna go read it πŸ“š
  • -qs {a|c|d|o|s|u|A|C|D|E|S} β€” this one lets you filter by queue instances in certain states. peep qstat(1) for the deets on states. 🌈
  • -U user,... β€” includes the queues that the specified users have access to in the qselect output. inclusive queen πŸ’œ

⭐ EXAMPLES ⭐

=====================================================

% qselect -l arch=linux
% qselect -l arch=linux -U andreas,shannon
% qconf -mattr queue h_vmem=1GB `qselect -l arch=linux`

=====================================================

okay so lemme walk you through this lil demo, because it's actually so good:

the first example prints the names of those queues residing on Linux machines. slay.

the second command in addition restricts the output to those queues with access permission for the users andreas and shannon. we love a filtered moment.

the third command changes the queue attribute h_vmem to 1 Gigabyte on queues residing on Linux machines. if you want the details on the -mattr option, check the qconf(1) manual page, and for details of queue configuration entries, hit up queue_conf(5). iykyk 🧚


🌸 ENVIRONMENT VARIABLES 🌸

  • SGE_ROOT β€” specifies the location of the Grid Engine standard configuration files. home base fr fr 🏠
  • SGE_CELL β€” if set, specifies the default Grid Engine cell. to address a Grid Engine cell, qselect uses these (in the order of precedence):
    • the name of the cell specified in the environment variable SGE_CELL, if it is set.
    • the name of the default cell, i.e. default.
  • SGE_DEBUG_LEVEL β€” if set, specifies that debug information should be written to stderr. in addition, the level of detail in which debug information is generated is defined. she's chatty πŸ’¬
  • SGE_QMASTER_PORT β€” if set, specifies the tcp port on which sge_qmaster(8) is expected to listen for communication requests. most installations will use a services map entry for the service "sge_qmaster" instead to define that port. noted πŸ“

πŸ“ FILES πŸ“

  • <sge_root>/<cell>/common/act_qmaster β€” Grid Engine master host file. the source of truth, periodt πŸ’«

🫢 SEE ALSO 🫢

sge_intro(1), qconf(1), qmod(1), qstat(1), queue_conf(5),

go read them, they're all part of the fam πŸ’–


see sge_intro(1) for a full statement of rights and permissions. legal besties, we respect them ✨


aaaand that's the whole page, babe πŸŽ€ this was SGE 8.1.3pre, dated 2012-01-04, and it ate. literally. go select some queues, you've got this πŸ’…πŸ’–