ACCESS_LIST(5)

NAME
access_list - Grid Engine Enterprise Edition access list file format

DESCRIPTION
Access lists are used in Grid Engine Enterprise Edition to define access permissions of users to queues (see or parallel environments (see A list of currently configured access lists can be displayed via the -sul option. The contents of each enlisted access list can shown via the -su switch. The output follows the access_list format description. New access lists can be created and existing can be modified via the -au and -du options to

Grid Engine Enterprise Edition departments are a special form of access list and allow in addition assignment of functional shares and override tickets.

FORMAT
The following list of access_list parameters specifies the access_list content:

  name
The name of the access list.

  type
This parameter is only available in a Grid Engine Enterprise Edition system. Grid Engine does not support this parameter.

The type of the acess 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 access list only or as a department.

  oticket
This parameter is only available in a Grid Engine Enterprise Edition system. Grid Engine does not support this parameter.

The amount of override tickets currently assigned to the department.

  fshare
This parameter is only available in a Grid Engine Enterprise Edition system. Grid Engine does not support this parameter.

The current functional share of the department.

  entries
The entries parameter contains the comma separated list of those UNIX users or UNIX user groups that are assigned to the access list or the Grid Engine Enterprise Edition department. Only symbolic names are allowed. A group is differentiated from a user name by prefixing the group name with a '@' sign. Pure access lists allows enlisting any user or group in any access list.

With Grid Engine Enterprise Edition departments each user or group enlisted may be enlisted in only one department, to ensure a unique assignment of jobs to departments. To jobs whose users do not match with any of the users or groups enlisted under entries the defaultdepartment is assigned, if existing.

SEE ALSO

COPYRIGHT
See for a full statement of rights and permissions.