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

NAME

6       share_tree - Grid Engine share tree file format
7

DESCRIPTION

9       The   share   tree  defines  the  long-term  resource  entitlements  of
10       users/projects and of a hierarchy of arbitrary groups thereof.
11
12       The current share tree  can  be  displayed  via  the  qconf(1)  -sstree
13       option.  The  output follows the share_tree format description. A share
14       tree can be created and an existing can be modified via the -astree and
15       -mstree  options  to qconf(1).  The -sst option shows a formatted share
16       tree (tree view).  Individual share tree nodes can  be  created,  modi‐
17       fied,  deleted,  or  shown  via  the  -astnode, -dstnode, -mstnode, and
18       -sstnode 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       The format of a share tree file is defined as follows:
26
27       ·  A new node starts with the attribute id,  and  equal  sign  and  the
28          numeric  identification  number  of  the node. Further attributes of
29          that node follow until another id-keyword is encountered.
30
31       ·  The attribute type defines, if a sharetree node  references  a  user
32          (type=0), or a project (type=1)
33
34       ·  The  attribute  childnodes  contains a comma separated list of child
35          nodes to this node.
36
37       ·  The parameter name refers to an arbitrary name for the node or to  a
38          corresponding  user (see user(5)) or project (see project(5)) if the
39          node is a leaf node of the share tree. The name for the root node of
40          the tree is "Root" by convention.
41
42       ·  The  parameter  shares defines the share of the node among the nodes
43          with the same parent node.
44
45       ·  A user leaf node named 'default' can be defined as a descendant of a
46          project(5))  node  in  the  share tree. The default node defines the
47          number of shares for users  who are running in the project, but  who
48          do  not have a user node defined under the project. The default user
49          node is a convenient way of specifying a single node for  all  users
50          which  should  receive  an equal share of the project resources. The
51          default node may be specified by itself or with other user(5)) nodes
52          at  the  same  level  below a project. All users, whether explicitly
53          specified as a user node or those which map to  the  'default'  user
54          node  must  have a corresponding user(5)) object defined in order to
55          get shares. Do not configure a user(5)) object named 'default'.
56
57

EXAMPLES

59       Jobs of projects P1 and P2 get 50 shares, all other jobs get 10 shares.
60
61       id=0
62       name=Root
63       type=0
64       shares=1
65       childnodes=1,2,3
66       id=1
67       name=P1
68       type=1
69       shares=50
70       childnodes=NONE
71       id=2
72       name=P2
73       type=1
74       shares=50
75       childnodes=NONE
76       id=3
77       name=default
78       type=0
79       shares=10
80       childnodes=NONE
81

SEE ALSO

83       ge_intro(1), qconf(1), project(5), user(5).
84

86       See ge_intro(1) for a full statement of rights and permissions.
87
88
89
90GE 6.2u5                 $Date: 2009/05/28 16:56:20 $            SHARE_TREE(5)
Impressum