1ACCESS_LIST(5)             Grid Engine File Formats             ACCESS_LIST(5)
2
3
4

NAME

6       access_list - Grid Engine access list file format
7

DESCRIPTION

9       Access  lists  are  used in Grid Engine to define access permissions of
10       users to queues  (see  queue_conf(5))  or  parallel  environments  (see
11       ge_pe(5)).   A  list  of  currently configured access lists can be dis‐
12       played via the qconf(1) -sul option.  The  contents  of  each  enlisted
13       access  list  can  shown  via  the  -su  switch. The output follows the
14       access_list format description. New access lists  can  be  created  and
15       existing can be modified via the -au and -du options to qconf(1).
16
17       Departments  are  a special form of access list that additionally allow
18       assignment of functional shares and override tickets.
19
20       Note, Grid Engine allows backslashes (\)  be  used  to  escape  newline
21       (\newline)  characters. The backslash and the newline are replaced with
22       a space (" ") character before any interpretation.
23

FORMAT

25       The following list of access_list parameters specifies the  access_list
26       content:
27
28   name
29       The   name   of   the  access  list  as  defined  for  userset_name  in
30       sge_types(1).
31
32   type
33       The type of the access list, currently  one  of ACL, or DEPT or a  com‐
34       bination of both in a comma separated list. Depending on this parameter
35       the access list can be used as access list only or as a department.
36
37   oticket
38       The amount of override tickets currently assigned to the department.
39
40   fshare
41       The current functional share of the department.
42
43   entries
44       The entries parameter contains the comma separated list of  those  UNIX
45       users (see user_name in sge_types(1)) or those primary UNIX groups that
46       are assigned to the access list or the department. Only a  user's  pri‐
47       mary  UNIX  group  is used; secondary groups are ignored. Only symbolic
48       names are allowed.  A group is differentiated from a user name by  pre‐
49       fixing the group name with a '@' sign.  Pure access lists allow enlist‐
50       ing any user or group in any access list.
51
52       When using departments,  each  user  or  group  enlisted  may  only  be
53       enlisted  in  one department, in order to ensure a unique assignment of
54       jobs to departments.  To jobs whose users do not match with any of  the
55       users  or  groups  enlisted  under  entries  the  defaultdepartment  is
56       assigned, if existing.
57

SEE ALSO

59       ge_intro(1), sge_types(1), qconf(1), ge_pe(5), queue_conf(5).
60

62       See ge_intro(1) for a full statement of rights and permissions.
63
64
65
66GE 6.2u5                 $Date: 2008/03/06 09:38:09 $           ACCESS_LIST(5)
Impressum