sge_access_list(5) [debian man page]

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

NAME

       access_list - Sun Grid Engine access list file format

DESCRIPTION

       Access  lists are used in Sun Grid Engine to define access permissions of users to queues (see queue_conf(5)) or parallel environments (see
       sge_pe(5)).  A list of currently configured access lists can be displayed via the qconf(1) -sul	option.  The  contents	of  each  enlisted
       access list can shown via the -su switch. The output follows the access_list format description. New access lists can be created and exist-
       ing can be modified via the -au and -du options to qconf(1).

       Departments are a special form of access list that additionally allow assignment of functional shares and override tickets.

       Note, Sun Grid Engine allows backslashes () be used to escape newline (
ewline) characters. The backslash and the  newline  are  replaced
       with a space (" ") character before any interpretation.

FORMAT

       The following list of access_list parameters specifies the access_list content:

   name
       The name of the access list as defined for userset_name in sge_types(1).

   type
       The type of the access list, currently  one  of ACL, or DEPT or a  combination of both in a comma separated list. Depending on this parame-
       ter the access list can be used as access list only or as a department.

   oticket
       The amount of override tickets currently assigned to the department.

   fshare
       The current functional share of the department.

   entries
       The entries parameter contains the comma separated list of those UNIX users (see user_name in sge_types(1)) or those  primary  UNIX  groups
       that  are  assigned to the access list or the department. Only a user's primary UNIX group is used; secondary groups are ignored. Only sym-
       bolic names are allowed.  A group is differentiated from a user name by prefixing the group name with a '@' sign.  Pure access lists  allow
       enlisting any user or group in any access list.

       When  using departments, each user or group enlisted may only be enlisted in one department, in order to ensure a unique assignment of jobs
       to departments.	To jobs whose users do not match with any of the users or groups enlisted under entries the defaultdepartment is assigned,
       if existing.

SEE ALSO

       sge_intro(1), sge_types(1), qconf(1), sge_pe(5), queue_conf(5).

COPYRIGHT

       See sge_intro(1) for a full statement of rights and permissions.

SGE 6.2u5							      $Date$							    ACCESS_LIST(5)

SHARE_TREE(5)						   Sun Grid Engine File Formats 					     SHARE_TREE(5)

NAME

       share_tree - Sun Grid Engine share tree file format

DESCRIPTION

       The share tree defines the long-term resource entitlements of users/projects and of a hierarchy of arbitrary groups thereof.

       The current share tree can be displayed via the qconf(1) -sstree option. The output follows the share_tree format description. A share tree
       can be created and an existing can be modified via the -astree and -mstree options to qconf(1).	The -sst option shows  a  formatted  share
       tree (tree view).  Individual share tree nodes can be created, modified, deleted, or shown via the -astnode, -dstnode, -mstnode, and -sstn-
       ode options to qconf(1).

       Note, Sun Grid Engine allows backslashes () be used to escape newline (
ewline) characters. The backslash and the  newline  are  replaced
       with a space (" ") character before any interpretation.

FORMAT

       The format of a share tree file is defined as follows:

       o  A  new  node	starts with the attribute id, and equal sign and the numeric identification number of the node. Further attributes of that
	  node follow until another id-keyword is encountered.

       o  The attribute type defines, if a sharetree node references a user (type=0), or a project (type=1)

       o  The attribute childnodes contains a comma separated list of child nodes to this node.

       o  The parameter name refers to an arbitrary name for the node or to a corresponding user (see user(5)) or project (see project(5)) if  the
	  node is a leaf node of the share tree. The name for the root node of the tree is "Root" by convention.

       o  The parameter shares defines the share of the node among the nodes with the same parent node.

       o  A  user  leaf  node named 'default' can be defined as a descendant of a project(5)) node in the share tree. The default node defines the
	  number of shares for users  who are running in the project, but who do not have a user node defined under the project. The default  user
	  node	is  a  convenient  way of specifying a single node for all users which should receive an equal share of the project resources. The
	  default node may be specified by itself or with other user(5)) nodes at the same level below a project. All  users,  whether	explicitly
	  specified as a user node or those which map to the 'default' user node must have a corresponding user(5)) object defined in order to get
	  shares. Do not configure a user(5)) object named 'default'.

EXAMPLES

       Jobs of projects P1 and P2 get 50 shares, all other jobs get 10 shares.

       id=0
       name=Root
       type=0
       shares=1
       childnodes=1,2,3
       id=1
       name=P1
       type=1
       shares=50
       childnodes=NONE
       id=2
       name=P2
       type=1
       shares=50
       childnodes=NONE
       id=3
       name=default
       type=0
       shares=10
       childnodes=NONE

SEE ALSO

       sge_intro(1), qconf(1), project(5), user(5).

COPYRIGHT

       See sge_intro(1) for a full statement of rights and permissions.

SGE 6.2u5							      $Date$							     SHARE_TREE(5)