SGE_QMASTER(8)

💖 SGE_QMASTER(8) — Grid Engine Administrative Commands 💖

okay bestie, sit down, hydrate, and let me tell you about sge_qmaster — the Grid Engine master control daemon ✨

---

🌸 NAME 🌸

sge_qmaster — the Grid Engine master control daemon 👑 like, the actual main character of your cluster

---

🎀 SYNOPSIS 🎀

sge_qmaster [ -help ]

---

🦋 DESCRIPTION 🦋

So <pink>sge_qmaster</pink> controls the overall Grid Engine behavior in a cluster. That's it, that's the whole vibe — it runs the whole show. no cap 💅

---

✨ OPTIONS ✨

• -help — prints a listing of all options. like, all of them. just for you 🫶

---

💜 ENVIRONMENT VARIABLES 💜

the way that these env vars run your entire life… obsessed

• SGE_ROOT — specifies the location of the Grid Engine standard configuration files.
• SGE_CELL — if set, specifies the default Grid Engine cell. To address a Grid Engine cell, sge_qmaster uses these 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 set, specifies that debug information should be written to stderr. In addition, the level of detail in which debug information is generated is defined by the defined value.
• SGE_DEBUG_LEVEL — if set, the qmaster will not daemonize.

yes bestie, it's listed twice in the original and I am nothing if not a faithful narrator 💀 same name, different job. iconic honestly.

• 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.
• SGE_EXECD_PORT — if set, specifies the tcp port on which sge_execd(8) is expected to listen for communication requests. Most installations will use a services map entry for the service "sge_execd" instead to define that port.
• SGE_TEST_DELAY_SCHEDULING — if set, specifies a delay in (integral seconds) before a scheduling run, for test purposes.
• SGE_ND — if set, don't daemonize the program (for debugging).
• SGE_ENABLE_COREDUMP — if set, enable core dumps on Linux when the admin_user is not root. Linux normally disables core dumps when the daemon has changed uid or gid. Setting SGE_ENABLE_COREDUMP in sge_qmaster's environment defeats that to enable core dumps for debugging if they are otherwise allowed. This is typically not a big hazard with SGE, since most information is exposed in the spool area anyhow. Dumps will appear in the host spool directory. On Solaris, coreadm(1) may be used to enable such dumps.
• SGE_QMASTER_PIDFILE — path name of file to which to write the daemon process id at startup (default "qmaster.pid"). Note that this must be writable by the admin user (see bootstrap(5)).

---

💀 RESTRICTIONS 💀

<pink>sge_qmaster</pink> is usually started from root on the master or shadow master machines of the cluster. If started by a normal user, a master spool directory must be used to which the user has read/write access. In this case, only jobs being submitted by that same user are handled correctly by the system.

fr fr, read that again before you go running it as yourself 🙈

---

🌈 FILES 🌈

• <sge_root>/<cell>/common/configuration — Grid Engine global configuration
• <sge_root>/<cell>/common/local_conf/<host> — Grid Engine host specific configuration
• <sge_root>/<cell>/common/qmaster_args — sge_qmaster argument file
• <sge_root>/<cell>/spool — default master spool directory

---

🔥 SEE ALSO 🔥

sge_intro(1), sge_conf(5), sge_execd(8), sge_shadowd(8)

---

⭐ COPYRIGHT ⭐

See sge_intro(1) for a full statement of rights and permissions.

---

and that's the whole page bestie, you ate it 💅✨ this was SGE 8.1.3pre, dated 2008-05-05 — go forth and daemonize responsibly, mwah 🎀🦋💖