1USER(5) Grid Engine File Formats USER(5)
2
3
4
6 user - Grid Engine user entry file format
7
9 A user entry is used to store ticket and usage information on a per
10 user basis. Maintaining user entries for all users participating in a
11 Grid Engine system is required if Grid Engine is operated under a user
12 share tree policy.
13
14 If the enforce_user cluster configuration parameter is set to auto, a
15 user object for the submitting user will be created automatically dur‐
16 ing job submission, if one does not already exist. The
17 auto_user_oticket, auto_user_fshare, auto_user_default_project, and
18 auto_user_delete_time cluster configuration parameters will be used as
19 default attributes of the new user object.
20
21 A list of currently configured user entries can be displayed via the
22 qconf(1) -suserl option. The contents of each enlisted user entry can
23 be shown via the -suser switch. The output follows the user format
24 description. New user entries can be created and existing can be modi‐
25 fied via the -auser, -muser and -duser options to qconf(1).
26
27 Note: Grid Engine allows backslashes (\) be used to escape newline
28 (\newline) characters. The backslash and the newline are replaced with
29 a space (" ") character before any interpretation.
30
32 A user entry contains four parameters:
33
34 name
35 The user name as defined for user_name in sge_types(1).
36
37 oticket
38 The amount of override tickets currently assigned to the user.
39
40 fshare
41 The current functional share of the user.
42
43 default_project
44 The default project of the user.
45
46 delete_time
47 The wall-clock time when this user will be deleted, expressed as the
48 number of seconds elapsed since January 1, 1970. If set to zero, the
49 affected user is a permanent user. If set to one, the user currently
50 has active jobs. For additional information about automatically cre‐
51 ated users, see the enforce_user and auto_user_delete_time parameters
52 in sge_conf(5).
53
55 sge_intro(1), sge_types(1), qconf(1). sge_conf(5).
56
58 See sge_intro(1) for a full statement of rights and permissions.
59
60
61
62GE 6.1 $Date: 2007/06/26 22:21:11 $ USER(5)