sge_hostgroup(5) [debian man page]

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

NAME

       hostgroup - host group entry file format

DESCRIPTION

       A host group entry is used to merge host names to groups.  Each	host  group  entry  file defines one group. Inside a group definition file
       you can also reference to groups. These groups are called subgroups. A subgroup is referenced by the sign "@" as  first	character  of  the
       name.

       A  list	of  currently  configured  host group entries can be displayed via the qconf(1) -shgrpl option. The contents of each enlisted host
       group entry can be shown via the -shgrp switch. The output follows the hostgroup format description. New host group entries can be  created
       and existing can be modified via the -ahgrp, -mhgrp, -dhgrp and -?attr 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 host group entry contains following parameters:

   group_name
       The group_name defines the host group name. Host group names have to begin with	an  '@'  character  as	explained  for	hostgroup_name	in
       sge_types(5).

   hostlist
       The  name of all hosts and host groups (see host_identifier in sge_types(1)) which are member of the group. As list separators white-spaces
       are supported only. Default value for this parameter is NONE.

       Note, if the first character of the host_identifier is an "@" sign the name is used to reference a hostgroup(5) which is taken as sub group
       of this group.

EXAMPLE

       This is a typical host group entry:

       group_name @bigMachines

       hostlist @solaris64 @solaris32 fangorn balrog

       The  entry  will  define  a new host group called @bigMachines. In this host group are the host fangorn, balrog and all members of the host
       groups @solaris64 and @solaris32.

SEE ALSO

       sge__types(1), qconf(1)

COPYRIGHT

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

SGE 6.2u5							      $Date$							      HOSTGROUP(5)

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)