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

NAME

6       project - Grid Engine project entry file format
7

DESCRIPTION

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 listed project definition
16       can be shown via the -sprj switch. The output follows the project  for‐
17       mat  description. New projects can be created and existing can be modi‐
18       fied 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

FORMAT

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 allowed to submit jobs to the project.
39
40   xacl
41       A  list  of  user access lists (ACLs - see access_list(5)) referring to
42       those users not allowed to submit jobs to the project.
43

SEE ALSO

45       sge_intro(1), sge_types(1), qconf(1), access_list(5).
46

48       See sge_intro(1) for a full statement of rights and permissions.
49
50
51
52GE 6.1                   $Date: 2007/06/26 22:21:11 $               PROJECT(5)
Impressum