ACCESS_LIST(5)

💖 ACCESS_LIST(5) — the Grid Engine access list file format, bestie edition 💖

okay so this is access_list(5), straight out of the Grid Engine File Formats manual, and it's literally the file format that decides who gets in to your cluster things. Let's go 🦋

---

✨ NAME ✨

access_list — the Grid Engine access list file format. that's it, that's the whole name, short and iconic 👑

---

🌸 DESCRIPTION 🌸

Access lists are what Grid Engine uses to define access permissions of users to all the places, bestie. Specifically:

• queues — peek queue_conf(5)
• parallel environments — peek sge_pe(5)
• execution hosts — peek host_conf(5)
• or the whole entire cluster — peek sge_conf(5)

Want to see which access lists are currently configured? Slay, just run qconf(1) with the -sul option. Want to see what's inside one of them? The -su switch has you covered, and its output follows exactly this access_list format description. Making a new one or editing an existing one? That's -au and -du on qconf(1), go off 💅

Departments are a special lil form of access list that additionally let you assign functional shares and override tickets. main character energy fr fr.

⚠️ Heads up: Grid Engine lets backslashes (\) escape newline characters. The backslash and the newline both get replaced with a space character before anything is interpreted. No cap, that happens before any interpretation. 🫶

---

🎀 FORMAT 🎀

Here's the whole list of access_list parameters that make up the access_list content:

name

The name of the access list, in the format used for userset_name in sge_types(5). 💖

type

The type of the access list. Right now it's one of ACL, or DEPT, or a combo of both in a comma-separated list. Depending on this parameter, your access list can be used as an access list only, or as a department. Choose your fighter ✨

oticket

The number of override tickets currently assigned to the department. 🎟️

fshare

The current functional share of the department. 🍓

entries

A comma-separated list of those UNIX users (see user_name in sge_types(5)) or those primary UNIX groups that are assigned to the access list or the department.

• Only a user's primary UNIX group is used — secondary groups are ignored, sorry bestie 😭
• Only symbolic names are allowed, no numbers
• A group is differentiated from a user name by prefixing the group name with an @ sign
• Pure access lists allow listing any user or group in any access list 🔥

Now for the department tea 🫖: when you're using departments, each user or group may only be listed in one department, and that's to ensure a unique assignment of jobs to departments. One department per user, periodt.

And if the defaultdepartment is defined, it gets assigned to jobs whose users don't match any of the users or groups listed under entries. The leftovers get adopted, basically 🥺

---

👑 SEE ALSO 👑

sge_intro(1), sge_types(5), qconf(1), sge_pe(5), queue_conf(5).

---

💜 COPYRIGHT 💜

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

---

and that's the whole page, bestie!! this version is from SGE 8.1.3pre, dated 2011-05-19 — yeah it's a lil vintage but she still ate 💖✨ stay hydrated, go read queue_conf(5) next 🦋🌸