SGE_PASSWD(1)

✨ SGE_PASSWD ✨

okay bestie, listen up — this is sgepasswd(1), a lil user command from the Grid Engine family, and it's basically the bouncer for your Grid Engine password file. 💅

---

🌸 NAME 🌸

sgepasswd — modify the Grid Engine password file of Grid Engine 🎀

---

🦋 SYNTAX 🦋

sgepasswd [[ -D domain ] -d user ]

sgepasswd [ -D domain ] [ user ]

---

💖 DESCRIPTION 💖

So sgepasswd modifies the Grid Engine password file, aka sgepasswd(5). iconic

That file holds a whole list of usernames plus their Microsoft Windows password, all in encrypted form. And who's out here reading it? sge_execd(8) and sge_shepherd(8) — but only on hosts running Microsoft Windows as their operating system — because they need that info to start jobs for a certain user. 🫶

Every user can use the sgepasswd application to add a new entry for their own user account. (plot twist: normal users can actually create an entry for any account, so like... the entry should be made initially, when the account is created. noted. 📝) And yes, you can also change the stored password with sgepasswd if the user knows the old one. know your password, bestie, that's the vibe check.

The root user gets extra main character energy: root additionally has permission to change the password entries for other user accounts. Root can also delete existing entries. 👑

Heads up! The sgepasswd binary is only available on non-Windows hosts. 🚫🪟

---

✨ OPTIONS ✨

• -D domain — By default, sgepasswd will add/modify the current Unix username without a domain specification. This switch can be used to add a domain specification in front of the current user name. Consult your Microsoft Windows documentation to get more information about domain users. 🌐
• -d user — Only root can use this parameter to delete entries from the sgepasswd(5) file. 🗑️
• -help — Prints a listing of all options. 📋

---

⚠️ NOTE ⚠️

Prevent relevant jobs running before a password is changed both with sgepasswd and in the Windows domain.

Otherwise, if multiple jobs try to run on a Windows host as the user concerned, and are unable to access the right password, Windows' intrusion detection system may disable the account. 💀 Like, not the cute kind of locked out.

sgepasswd and in the Windows domain.

yeah, that last bit is literally what the page says — don't come for me, I'm just the messenger 💅

---

🔒 SECURITY 🔒

This is a non-trivial program which needs to be setuid root, operating with various user-supplied input. It probably shouldn't be installed setuid if it is not needed to support Windows hosts. 😭

See above concerning making initial entries. ⬆️

---

🌈 ENVIRONMENT VARIABLES 🌈

• SGE_CERTFILE — Specifies the location of the public key file. By default sgepasswd will use $SGE_ROOT/$SGE_CELL/common/sgeCA/certs/cert.pem. 🔑
• SGE_KEYFILE — If set, specifies the location of the private key file. Default is /var/lib/sgeCA/port$SGE_QMASTER_PORT/$SGE_CELL/private/key.pem. 🗝️
• SGE_RANDFILE — If set, specifies the location of the seed used to create encrypted versions of user passwords. Default is /var/lib/sgeCA/port${SGE_QMASTER_PORT}/${SGE_CELL}/private/rand.seed. 🎲

---

👀 SEE ALSO 👀

sge_intro(1), sgepasswd(5)

---

📜 COPYRIGHT 📜

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

---

and that's the whole page, bestie — no cap, every flag, every path, every default accounted for. 🫶

sending u off with the receipts: this was SGE 8.1.3pre, dated 2012-02-17, filed under SGE_PASSWD(1). mwah 💅✨