1PROJECT(5) Grid Engine File Formats PROJECT(5)
2
3
4
6 project - Grid Engine project entry file format
7
9 Jobs can be submitted to projects, and a project can be assigned with a
10 certain level of importance via the functional or the override policy.
11 This level of importance is then inherited by the jobs executing under
12 that project.
13
14 A list of currently configured projects can be displayed via the
15 qconf(1) -sprjl option. The contents of each enlisted project definiā
16 tion can be shown via the -sprj switch. The output follows the project
17 format description. New projects can be created and existing can be
18 modified via the -aprj, -mprj and -dprj options to qconf(1).
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
25 A project definition contains the following parameters:
26
27 name
28 The project name as defined for project_name in sge_types(1).
29
30 oticket
31 The amount of override tickets currently assigned to the project.
32
33 fshare
34 The current functional share of the project.
35
36 acl
37 A list of user access lists (ACLs - see access_list(5)) referring to
38 those users being allowed to submit jobs to the project.
39
40 If the acl parameter is set to NONE, all users are allowed to submit
41 jobs to the project except for those listed in xacl parameter described
42 below.
43
44 xacl
45 A list of user access lists (ACLs - see access_list(5)) referring to
46 those users being not allowed to submit jobs to the project.
47
49 ge_intro(1), ge_types(1), qconf(1), access_list(5).
50
52 See ge_intro(1) for a full statement of rights and permissions.
53
54
55
56GE 6.2u5 $Date: 2009/01/13 10:15:29 $ PROJECT(5)