project - Grid Engine project entry file format

See sge_intro(1) for a full statement of rights and permissions. SGE 8.1.3pre $Date: 2011-05-17 21:12:00 $ PROJECT(5)

Jobs can be submitted to projects, and a project can be assigned with a certain level of importance, via the functional or the override policy. This level of importance is then inherited by the jobs executing under that project. A list of currently configured projects can be displayed via the qconf(1) -sprjl option. The contents of each listed project definition can be shown via the -sprj switch. The output follows the project format description. New projects can be created, and existing ones can be modified, via the -aprj, -mprj and -dprj options to qconf(1). Note, Grid Engine allows backslashes (\) be used to escape newline characters. The backslash and the newline are replaced with a space character before any interpretation.

A project definition contains the following parameters: name The project name in the format for project_name in sge_types(5). oticket The number of override tickets currently assigned to the project. fshare The current functional share of the project. acl A list of user access lists (ACLs - see access_list(5)) referring to those users allowed to submit jobs to the project. If the acl parameter is set to NONE, all users are allowed to submit jobs to the project except for those listed in the xacl parameter described below. xacl A list of user access lists (ACLs - see access_list(5)) referring to those users not allowed to submit jobs to the project.

project - Grid Engine project entry file format

sge_intro(1), sge_types(1), qconf(1), access_list(5).