DESCRIPTIONAccess lists are used in Grid Engine to define access permissions of users to queues (see parallel environments (see execution hosts (see or the whole cluster ( see A list of currently configured access lists can be displayed via the -sul option. The contents of each access list can shown via the -su switch. The output follows the access_list format description. New access lists can be created and existing ones can be modified via the -au and -du options to
Departments are a special form of access list that additionally allow assignment of functional shares and override tickets.
Note, Grid Engine allows backslashes (\) be used to escape newline characters. The backslash and the newline are replaced with a space character before any interpretation.
FORMATThe following list of access_list parameters specifies the access_list content:
nameThe name of the access list in the format for userset_name in
typeThe type of the access list, currently one of ACL, or DEPT or a combination of both in a comma-separated list. Depending on this parameter, the access list can be used as an access list only, or as a department.
oticketThe number of override tickets currently assigned to the department.
fshareThe current functional share of the department.
entriesA comma-separated list of those UNIX users (see user_name in 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. Only symbolic names are allowed. A group is differentiated from a user name by prefixing the group name with a '@' sign. Pure access lists allow listing any user or group in any access list.
When using departments, each user or group may only be listed in one department, in order to ensure a unique assignment of jobs to departments. If the defaultdepartment is defined, it is assigned to jobs whose users do not match with any of the users or groups listed under entries.
COPYRIGHTSee for a full statement of rights and permissions.