SGE_INTRO(1)

✨ SGE_INTRO(1) — the Grid Engine glow-up ✨

okay bestie, sit down, hydrate, because this is the Grid Engine User Commands manual page and it's literally the whole vibe of the cluster in one doc 💖

🌸 NAME 🌸

sge_intro — Grid Engine, a facility for executing jobs on remote machines

🦋 DESCRIPTION 🦋

so like, Grid Engine is a whole facility for executing Unix-like batch jobs (shell scripts or binaries, yes both) on a pool of cooperating CPUs. Jobs get queued and executed remotely according to defined policies. no cap.

and the CPUs? they might be sitting in desktop systems, with jobs run on them at times when they'd otherwise be idle or only lightly loaded. the way that works is the work load may be distributed according to the (generalized) load situation of each machine and the resource requirements of the jobs. it's giving "your coworker's desktop is doing your homework while they're at lunch" energy fr fr.

user level checkpointing programs are supported and a transparent checkpointing mechanism is provided (see sge_ckpt(1)). checkpointing jobs migrate from system to system without user intervention on load demand — iconic, they just move on their own 💅.

and not just simple batch jobs: interactive jobs and parallel jobs can also be submitted to Grid Engine. main character energy for every job type.

👑 USER INTERFACE 👑

the Grid Engine user interface consists of several programs which are described separately. here's the whole friend group 🫶

• qacct(1) — qacct extracts arbitrary accounting information from the cluster logfile. receipts, literally.
• qalter(1) — qalter changes the characteristics of already submitted jobs. glow-up a job after you already sent it.
• qconf(1) — qconf provides the user interface for configuring, modifying, deleting and querying queues and the cluster configuration.
• qdel(1) — qdel provides the means for a user/operator/manager to cancel jobs. bye bestie 👋
• qevent(1) — qevent provides a means of watching Grid Engine events and acting on jobs finishing.
• qhold(1) — qhold holds back submitted jobs from execution. not yet, we're not ready.
• qhost(1) — qhost displays status information about Grid Engine execution hosts.
• qlogin(1) — qlogin initiates a telnet or similar login session with automatic selection of a suitable host.
• qmake(1) — qmake is a replacement for the standard Unix make facility. It extends make with an ability to distribute independent make steps across a cluster of suitable machines. parallel make? slay.
• qmod(1) — qmod allows the owner(s) of a queue to suspend and enable queues, e.g. all queues associated with his machine (all currently active processes in this queue are also signaled) or to suspend and enable jobs executing in the queues.
• qmon(1) — qmon provides a Motif command interface to all Grid Engine functions. The status of all, or a private selection of, the configured queues is displayed on-line by changing colors at corresponding queue icons. color-coded queue icons?? obsessed 😭
• qping(1) — qping can be used to check the status of Grid Engine daemons. vibe check, but for daemons.
• qquota(1) — qquota provides a status listing of all currently used resource quotas (see sge_resource_quota(5)).
• qresub(1) — qresub creates new jobs by copying currently running or pending jobs.
• qrls(1) — qrls releases holds from jobs previously assigned to them e.g. via qhold(1) (see above).
• qrdel(1) — qrdel provides the means to cancel advance reservations.
• qrsh(1) — qrsh can be used for various purposes such as providing remote execution of interactive applications via Grid Engine comparable to the standard Unix facility rsh, to allow for the submission of batch jobs which, upon execution, support terminal I/O (standard/error output and standard input) and terminal control, to provide a batch job submission client which remains active until the job has finished or to allow for the Grid Engine-controlled remote execution of the tasks of parallel jobs. multi-talented fr fr.
• qrstat(1) — qrstat provides a status listing of all advance reservations in the cluster.
• qrsub(1) — qrsub is the user interface for submitting an advance reservation to Grid Engine.
• qselect(1) — qselect prints a list of queue names corresponding to specified selection criteria. The output of qselect is usually fed into other Grid Engine commands to apply actions on a selected set of queues. it's giving pipeline queen.
• qsh(1) — qsh opens an interactive shell (in an xterm(1)) on a low loaded host. Any kind of interactive job can be run in this shell.
• qstat(1) — qstat provides a status listing of all jobs and queues associated with the cluster.
• qtcsh(1) — qtcsh is a fully compatible replacement for the widely known and used Unix C-Shell (csh) derivative tcsh. It provides a command-shell with the extension of transparently distributing execution of designated applications to suitable and lightly loaded hosts via Grid Engine.
• qsub(1) — qsub is the user interface for submitting a job to Grid Engine. the moment you've all been waiting for 💖

🌈 SEE ALSO 🌈

sge_ckpt(1), qacct(1), qalter(1), qconf(1), qdel(1), qhold(1), qhost(1), qlogin(1), qmake(1), qmod(1), qmon(1), qresub(1), qrls(1), qrsh(1), qselect(1), qsh(1), qstat(1), qsub(1), qtcsh(1).

🎀 COPYRIGHT 🎀

Copyright: 2008 by Sun Microsystems, Inc. Parts of the manual page texts are Copyright 2011 Univa Corporation, and various dates by other contributors. The manual pages are licensed under the Sun Industry Standards Source License, like the source, except where noted in some files by other contributors, which are under other free licences noted in their source.

okay and that's the whole page bestie, every option, every program, every legal line, all of it 💜

and that's a wrap, my love 🧚 this was SGE 8.1.3pre, dated 2011-05-08, and you just read the entire SGE_INTRO(1) page. go submit something iconic ✨💅🍓