Setting Up a User

You need to perform the following tasks to set up a user for the Grid Engine system:

Assign required logins.
To submit jobs from host A for execution on host B, users must have identical accounts on both hosts. No login is required on the machine where sge_qmaster runs.

Set access permissions.
The Grid Engine software enables you to restrict user access to the entire cluster, to queues, and to parallel environments. See Configuring User Access for a detailed description.
In addition, you can grant users permission to suspend or enable certain queues. See How to Configure User Access Parameters for more information.

Declare a Grid Engine System user.
To add users to the share tree or to define functional or override policies for users, you must declare those users to the Grid Engine system. For more information, see Configuring Policy-Based Resource Management With QMON and Configuring User Objects With QMON.

Set up project access.
If projects are used for the definition of share-based, functional, or override policies, you should give the user access to one or more projects. Otherwise the user's jobs might end up in the lowest possible priority class, which would result in the jobs having access to very few resources. See Configuring Policy-Based Resource Management With QMON for more information.

Set file access restrictions.
Users of the Grid Engine system must have read access to the directory $SGE_ROOT/$SGE_CELL/common. Before a job starts, the execution daemon creates a temporary working directory for the job and changes ownership of the directory to the job owner. The execution daemon runs as root. The temporary directory is removed as soon as the job finishes. The temporary working directory is created under the path defined by the queue configuration parameter tmpdir. See the queue_conf(5) man page for more information.
Make sure that temporary directories can be created under the tmpdir location. The directories should be set to Grid Engine system user ownership. Users should be able to write to the temporary directories.

Set up site dependencies.
By definition, batch jobs do not have a terminal connection. Therefore UNIX commands like stty in the command interpreter's startup resource file (for example, .cshrc for csh) can lead to errors. Check for the occurrence of stty in startup files. Avoid the commands that are described in Verifying the Installation.
Because batch jobs are usually run off line, the Grid Engine system notifies users of error events in the following ways:
- Logs error messages to the Grid Engine system log file.
- Sends an email to the job owner. If the error log file can't be opened, email is the only way to notify the user of an error event. Therefore, the email system should be properly installed for Grid Engine users.

Set up Grid Engine system definition files.
You can set up the following definition files for Grid Engine users:
- qmon – Resource file for the Grid Engine system GUI. See Customizing QMON.
- sge_aliases – Aliases for the path to the current working directory. See Using Path Aliasing.
- sge_request – Default request definition file. See Configuring Default Requests.

Labels