USER(5)

💖 USER(5) — the Grid Engine user entry file format, bestie edition 🎀

ok so this is USER(5) from the Grid Engine File Formats manual. yes it's a whole file format, yes it's about you (well, about your user entry), and yes we're gonna make it make sense. sit down, grab a strawberry drink 🍓, let's go.

---

✨ NAME ✨

user — the Grid Engine user entry file format. that's it, that's the name, iconic 💅

---

🌸 DESCRIPTION 🌸

so a user entry is a lil record that stores ticket and usage info on a per-user basis. one entry per user, very personal, very main character energy.

and here's the thing: if you're running Grid Engine under a user share tree policy, you have to maintain user entries for all the users participating in the system. no skipping, no "she's not on the list", everybody gets an entry. periodt.

now, if the enforce_user cluster configuration parameter is set to auto, a user object for the submitting user gets created automatically during job submission — but only if one doesn't already exist. and when that happens, these cluster config parameters get used as the default attributes of the shiny new user object:

• auto_user_oticket
• auto_user_fshare
• auto_user_default_project
• auto_user_delete_time

slay, defaults handled for you 🫶

want to see who's who? you can list all the currently configured user entries with the qconf(1) -suserl option. and if you wanna peek inside any individual entry on that list, that's the -suser switch. the output follows the user format description (scroll down, bestie 👇). creating new user entries and modifying existing ones? that's -auser, -muser and -duser over in qconf(1). the whole toolkit fr fr.

⚠️ heads up: Grid Engine lets you use backslashes (\) to escape newline characters. the backslash and the newline get replaced with a space character before any interpretation happens. so like, don't be weird about it.

---

🦋 FORMAT 🦋

a user entry contains four parameters:

name

the user name, in the format for user_name in sge_types(5).

oticket

the number of override tickets currently assigned to the user.

fshare

the current functional share of the user.

default_project

the default project of the user.

delete_time

💀 Note: Deprecated, may be removed in future release.

the wall-clock time when this user will be deleted, expressed as the number of seconds elapsed since January 1, 1970. some very specific vibes:

• if set to zero, the affected user is a permanent user.
• if set to one, the user currently has active jobs.

for additional info about automatically created users, go read the enforce_user and auto_user_delete_time parameters in sge_conf(5). iykyk 📖

---

🌈 SEE ALSO 🌈

• sge_intro(1)
• sge_types(1)
• qconf(1)
• sge_conf(5)

---

👑 COPYRIGHT 👑

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

---

ok that's the whole page, you ate that. this was SGE 8.1.3pre, dated $Date: 2011-05-17 21:18:42 $, and it's filed under USER(5). go forth and manage your users, bestie 🧚✨