Cambios de precipitaciones según el escenario A2 del IEEE
Recuadro 15. Actividades para el manejo de tierras de pastoreo
8. Actividades para la adaptación y biodiversidad
■ To add a new operator account, type its name in the field above the operator
account list. Click Add or press the Return key.
■ To delete an operator account, select it, and then click Delete.
3.1.1.6 How to Configure User Access Lists From the Command Line
The administrator can define access permissions to queues and other facilities, such as parallel environment interfaces. Access can be restricted to certain users or user groups.
Departments are a special form of access list that assign functional shares and override tickets. A user may be assigned to only one department access list.
For the purpose of restricting access permissions, the administrator creates and maintains access lists (ACLs). The ACLs contain user names and UNIX group names. The ACLs are then added to access-allowed or access-denied lists in the queue or in the parallel environment interface configurations. Users who belong to ACLs that are listed in access-allowed-lists have permission to access the queue or the parallel environment interface. Users who are members of ACLs in access-denied-lists cannot access the resource in question.
ACLS can also be used to define projects, to which assigned users can submit their jobs. The administrator can also restrict access to cluster resources on a per project basis. For more information on projects, see "Configuring Projects".
3.1.1.6.1 Client Commands To configure user access lists from the command line, use the following arguments for the qconf command:
■ To display a user access list, type the following command: qconf -su <accesslistname> [,...]
The -su option (show user access list) displays the specified access lists.
■ To display all user access lists, type the following command: qconf -sul
The -sul option (show user access lists) displays all access lists currently defined.
■ To add a one or more users to an access list, type the following command: qconf -au <username> [,...] <accesslistname> [,...]
The -au option (add user) adds one or more users to the specified access lists. The Grid Engine software provides the following default accesslistnames:
■ arusers - The arusers access list restricts the use of qrsub to request an advance
reservation. Only users listed in this access list may use this option. For more information, see How to Enable a User to Create Advance Reservations From the Command Line.
■ deadlineusers - The deadlineusers access list restricts the use of the qsub
-dldate_time switch, which specifies the deadline initiation time. The deadline initiation time is the time at which a job has to reach top priority in order to be completed within a given deadline. Only usernames listed in the
deadlineusers access list are allowed to request this option. For more information, see Configuring the Urgency Policy.
■ To add a user access list from a file, type the following command: qconf -Au <filename>
The -Au option (add user access list from file) uses a configuration file, filename, to add an access list.
■ To modify a user access list, type the following command: qconf -mu <accesslistname>
The -mu option (modify user access list) modifies the specified access lists. For more information, see User Access List Configuration Parameters.
■ To modify a user list from file, type the following command: qconf -Mu <filename>
The -Mu option (modify user access list from file) uses a configuration file,
filename, to modify the specified access lists. For more information, see User Access List Configuration Parameters.
■ To delete one more users from an access list, type the following command: qconf -du <username> [,...] <accesslistname> [,...]
The -du option (delete user) deletes one or more users from the specified access lists.
■ To delete a user list, type the following command: qconf -dul <access-list-name> [,...]
The -dul option (delete user list) completely removes userset lists.
For more information on how to configure the cluster from file or how to modify many objects at once, see Using qconf.
3.1.1.7 User Access List Configuration Parameters
Access lists are used in Grid Engine to define access permissions of users to queues or parallel environments.
3.1.1.8 How to Configure User Access Lists With QMON
The administrator can define access permissions to queues and other facilities, such as parallel environment interfaces. Access can be restricted to certain users or user groups.
Departments are a special form of access list that assign functional shares and override tickets. A user may be assigned to only one department access list.
For the purpose of restricting access permissions, the administrator creates and maintains access lists (ACLs). The ACLs contain user names and UNIX group names. The ACLs are then added to access-allowed or access-denied lists in the queue or in the parallel environment interface configurations. Users who belong to ACLs that are listed in access-allowed-lists have permission to access the queue or the parallel environment interface. Users who are members of ACLs in access-denied-lists cannot access the resource in question.
ACLS can also be used to define projects, to which assigned users can submit their jobs. The administrator can also restrict access to cluster resources on a per project basis. For more information on projects, see "Configuring Projects".
3.1.1.8.1 Steps
■ On the QMON Main Control window, click the User Configuration button, and
then click the Userset tab. The Userset tab appears as shown in the following figure.
In the Grid Engine system, a userset can be either an access list, a Department, or both. The check boxes below the Usersets list indicate the type of the selected userset. This section describes access lists. Departments are explained in How to Configure User Objects From the Command Line. The Usersets list displays all available access lists. The Grid Engine software provides the following default access lists:
■ arusers - The arusers access list restricts the use of qrsub to request an advance
reservation. Only users listed in this access list may use this option. For more information, see How to Enable a User to Create Advance Reservations From the Command Line.
■ deadlineusers - The deadlineusers access list restricts the use of the qsub
-dldate_time switch, which specifies the deadline initiation time. The deadline initiation time is the time at which a job has to reach top priority in order to be completed within a given deadline. Only usernames listed in the
deadlineusers access list are allowed to request this option. For more information, see Configuring the Urgency Policy.
■ defaultdeparment - The defaultdepartment access list automatically includes
all users who are not assigned to an administrator-created department. For more information, see Configuring the Functional Policy.
To display currently defined users and groups, select the userset.
■ You can perform the following tasks from the Userset Tab:
■ To add a new userset, click Add. An Access List Definition dialog box appears,
as shown in the figure below. The Users/Groups list displays all currently defined users and groups.
– To add a new access list definition, type the name of the access list in the Userset Name field and click Ok.
– To add a new user or group to the access list, type a user or group name in the User/Group field and then click Ok. Be sure to prefix group names with an @ sign.
– To delete a user or group from the Users/Groups list, select it and then click the trash icon.
■ To modify an existing userset, select it, and then click Modify. An Access List
Definition dialog box appears with the name of the current userset in the Userset Name field.
■ To delete a userset, select it, and then click Delete.
■ To save your changes and close the dialog box, click OK. Click Cancel to close the
dialog box without saving changes.
3.1.1.9 How to Configure User Objects From the Command Line
To configure a user object from the command line, use the following arguments for the qconf command:
■ To display a the configuration for a specific user, type the following command: qconf -suser <username>
The -suser option (show user) displays the configuration of the specified user.
■ To display a list of all currently defined users, type the following command: qconf -suserl
The -suserl option (show user list) displays a list of all currently defined users.
■ To add a user, type the following command: qconf -auser
The -auser option (add user) opens a template user configuration in an editor. The editor is either the default vi editor or the editor specified by the EDITOR
environment variable. After you save your changes and exit the editor, the changes are registered with sge_qmaster.
■ To add a user from file, type the following command: qconf -Auser <filename>
The -Auser option (add user from file) parses the specified file and adds the user configuration. The file must have the format of the user configuration template.
■ To modify a user, type the following command: qconf -muser <username>
The -muser option (modify user) enables you to modify an existing user entry. The option loads the user configuration in an editor. From the editor, you can modify a user's configuration, including the user's default project. After you save your changes and exit the editor, the changes are registered with sge_qmaster. For more information, see User Configuration Parameters.
■ To modify a user from file, type the following command: qconf -Muser <filename>
The -Muser option (modify user from file) parses the specified file and modifies the user configuration. The file must have the format of the user configuration template. For more information, see User Configuration Parameters.
■ To delete a user, type the following command: qconf -duser <username> [,...]
The -duser option (delete user) deletes one or more user objects.
For more information on how to configure the cluster from file or how to modify many objects at once, see Using qconf.
3.1.1.10 User Configuration Parameters
A user entry is used to store ticket and usage information on a per user basis. Maintain user entries for all users participating in a Grid Engine system is required if Grid Engine is operated under a user share tree policy. For more information, see
Configuring the Share-Based Policy. Table 3–1 User Configuration Parameters
Parameter Description
name User name
oticket Amount of override tickets currently assigned to the user. fshare Functional share of the user.