ACCESS_LIST(5)             Grid Engine File Formats             ACCESS_LIST(5)



[1mNAME[0m
       access_list - Grid Engine access list file format

[1mDESCRIPTION[0m
       Access  lists  are  used in Grid Engine to define access permissions of
       users to queues  (see  [4mqueue_conf[24m(5))  or  parallel  environments  (see
       [4msge_pe[24m(5)).   A  list  of currently configured access lists can be dis-
       played via the [4mqconf[24m(1) [1m-sul [22moption. The contents of each listed access
       list  can  shown via the [1m-su [22mswitch. The output follows the [4maccess_list[0m
       format description. New access lists can be created and existing can be
       modified via the [1m-au [22mand [1m-du [22moptions to [4mqconf[24m(1).

       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
       (\newline)  characters. The backslash and the newline are replaced with
       a space (" ") character before any interpretation.

[1mFORMAT[0m
       The following list of [4maccess_list[24m parameters specifies the  [4maccess_list[0m
       content:

   [1mname[0m
       The   name   of   the  access  list  as  defined  for  [4muserset_name[24m  in
       [4msge_types[24m(1).

   [1mtype[0m
       The type of the access list, currently  one  of [4mACL,[24m or [4mDEPT[24m or a  com-
       bination 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.

   [1moticket[0m
       The amount of override tickets currently assigned to the department.

   [1mfshare[0m
       The current functional share of the department.

   [1mentries[0m
       The entries parameter contains the comma separated list of  those  UNIX
       users (see [4muser_name[24m in [4msge_types[24m(1)) or those primary UNIX groups that
       are assigned to the access list or the department. Only a  user's  pri-
       mary  UNIX  group  is used; secondary groups are ignored. Only symbolic
       names are allowed.  A group is differentiated from a user name by  pre-
       fixing 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 listed may only  be  in  one
       department,  in  order to ensure a unique assignment of jobs to depart-
       ments.  The [4mdefaultdepartment[24m [4m,[24m if it exists, is assigned to jobs whose
       users do not match with any of the users or groups listed in entries.

[1mSEE ALSO[0m
       [4msge_intro[24m(1), [4msge_types[24m(1), [4mqconf[24m(1), [4msge_pe[24m(5), [4mqueue_conf[24m(5).

[1mCOPYRIGHT[0m
       See [4msge_intro[24m(1) for a full statement of rights and permissions.



GE 6.1                   $Date: 2008/03/06 09:37:30 $           ACCESS_LIST(5)
