Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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)

Check Out this Related Man Page

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

NAME

       user - Sun Grid Engine user entry file format

DESCRIPTION

       A  user	entry is used to store ticket and usage information on a per user basis. Maintaining user entries for all users participating in a
       Sun Grid Engine system is required if Sun Grid Engine is operated under a user share tree policy.

       If the enforce_user cluster configuration parameter is set to auto, a user object for the submitting user  will	be  created  automatically
       during	job  submission,  if  one  does  not  already  exist.  The  auto_user_oticket,	auto_user_fshare,  auto_user_default_project,  and
       auto_user_delete_time cluster configuration parameters will be used as default attributes of the new user object.

       A list of currently configured user entries can be displayed via the qconf(1) -suserl option. The contents of each enlisted user entry  can
       be  shown  via the -suser switch. The output follows the user format description. New user entries can be created and existing can be modi-
       fied via the -auser, -muser and -duser 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

       A user entry contains four parameters:

   name
       The user name as defined for user_name in sge_types(1).

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

   fshare
       The current functional share of the user.

   default_project
       The default project of the user.

   delete_time
       Note: Deprecated, may be removed in future release.
       The  wall-clock	time when this user will be deleted, expressed as the number of seconds elapsed since January 1, 1970. If set to zero, the
       affected user is a permanent user. If set to one, the user currently has active jobs.  For additional information about automatically  cre-
       ated users, see the enforce_user and auto_user_delete_time parameters in sge_conf(5).

SEE ALSO

       sge_intro(1), sge_types(1), qconf(1).  sge_conf(5).

COPYRIGHT

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

SGE 6.2u5							      $Date$								   USER(5)
Man Page