USERMAPPING(5) File Formats Manual USERMAPPING(5)NAME
usermapping - user mapping entry file format
DESCRIPTION
A usermapping entry is used to define alias names for a cluster user. The user's name known by the scheduling system is known as the clus-
ter user. If the cluster user doesn't match the user account name on an execution host, the usermapping feature can solve the problem.
Each line in the usermapping entry file specifies a user name and the host(s) where he has an account.
A list of currently configured user mapping entries can be displayed via the qconf(1)-sumapl option. The contents of each enlisted user
mapping entry can be shown via the -sumap switch. The output follows the usermapping format description. New user entries can be created
and existing can be modified via the -aumap, -mumap and -dumap options to qconf(1).
FORMAT
A user mapping entry contains two parameters:
cluster_user
The cluster_user keyword defines the cluster user name. The rest of the textline after the keyword "cluster_user" will be taken as cluster
user value.
remote_user
The user name on an execution host. Please note that the value for this attribute might be overwritten for a certain hostgroups or single
host. Find an example below.
EXAMPLE
This is a typical user mapping entry for a cluster user mapping:
cluster_user peter
remote_user peter,[@linux=pet1],[fangorn=peter1]
The entry will map the user peter which is defined in the cluster system to the user peter on all hosts in the cluster except for all hosts
which are referenced in the hostgroup @linux. For all these hosts the user will be mapped to pet1. For the host fangorn the remote user
will be peter1. hostgroup(5) to obtain for more information about that.
SEE ALSO qconf(1), hostgroup(5).
COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions.
$Date$ USERMAPPING(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)