actions – Shorewall action declaration file Synopsis /etc/shorewall/actions Description This file allows you to define new ACTIONS for use in rules (see m[blue]shorewall-rules(5)m[][1]). You define the iptables rules to be performed in an ACTION in /etc/shorewall/action.action-name. Columns are: NAME The name of the action. ACTION names should begin with an upper-case letter to distinguish them…
accounting – Shorewall Accounting file Synopsis /etc/shorewall/accounting Description Accounting rules exist simply to count packets and bytes in categories that you define in this file. You may display these rules and their packet and byte counters using the shorewall show accounting command. Beginning with Shorewall 4.4.18, the accounting structure can be created with three root…
shigofumirc – Configuration file for Shigofumi Description Configuration for shigofumi is loaded from .shigofumirc in user’s home directory by default. The file is plain text file with simple syntax: Setting is stored in option = value format. If value is a type of string, it must be delimited by quotation marks. Boolean values can be…
shells – pathnames of valid login shells Description /etc/shells is a text file which contains the full pathnames of valid login shells. This file is consulted by chsh(1) and available to be queried by other programs. Be aware that there are programs which consult this file to find out if a user is a normal…
share_tree – xxQS_NAMExx share tree file format Description The share tree defines the long-term resource entitlements of users/projects and of a hierarchy of arbitrary groups thereof. Note that it is normally necessary to maintain users explicitly to use a share tree, rather than use automatic creation and (specifically) destruction, or at least set auto_user_delete_time to…
shadow – shadowed password file Description shadow is a file which contains the password information for the system’s accounts and optional aging information. This file must not be readable by regular users if password security is to be maintained. Each line of this file contains 9 fields, separated by colons (“:”), in the following order:…
sgepasswd – xxQS_NAMExx password file format Description sgepasswd contains a list of user names and their corresponding encrypted Microsoft Windows passwords. If available, the password file will be used by and To change the contents of this file please use the command. It is not advised to change the file manually. See Also Copyright See…
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 cluster user. If the cluster user doesn’t match the user account name on an execution host, the usermapping feature can solve the…
user – 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 Grid Engine system is required if Grid Engine is operated under a user share tree policy. If the enforce_user cluster configuration…
sge_types – xxQS_NAMExx type descriptions Description The xxQS_NAMExx user interface consists of several programs and files. Some command-line switches and several file attributes are types. The syntax for these types is explained in this page. Object Types These types are used for defining xxQS_NAMExx configuration: object_name An object name is a sequence of up to…
sge_status – xxQS_NAMExx job status values Description Job state The following table lists the job states shown by and returned by The DRMAA state corresponds to the DRMAA_PS_state value that may be returned by Category State SGE DRMAA state Pending pending qw, Rq QUEUED_ACTIVE pending, user hold hqw USER_ON_HOLD pending, system hold hqw SYSTEM_ON_HOLD pending,…
share_tree – Grid Engine share tree file format Description The share tree defines the long-term resource entitlements of users/projects and of a hierarchy of arbitrary groups thereof. The current share tree can be displayed via the -sstree option. The output follows the share_tree format description. A share tree can be created and an existing can…
sge_schedule – format of the xxQS_NAMExx schedule file Description The schedule file is written by the qmaster when MONITOR=1 is set in the params item of Note that the file tends to grow rapidly, and should be truncated/rotated, e.g. with logrotate(1). Also it should probably be placed on local disk, not an NFS-mounted filesystem, for…
sched_conf – Grid Engine default scheduler configuration file Description sched_conf defines the configuration file format for Grid Engine’s scheduler. In order to modify the configuration, use the graphical user’s interface or the -msconf option of the command. A default configuration is provided together with the Grid Engine distribution package. Note, Grid Engine allows backslashes (\)…
xxqs_name_sxx_resource_quota – xxQS_NAMExx resource quota file format Description Resource quota sets (RQS) are a flexible way to set a maximum resource consumption for any job requests. They are used by the scheduler to select the next possible jobs for running. The job request quota application is done according to a set of user, project, cluster…
xxqs_name_sxx_request – xxQS_NAMExx default request definition file format Description xxqs_name_sxx_request reflects the format of the files defining default request profiles. These apply to and but for convenience, only qsub is mentioned below. If available, default request files are read and processed during job submission, before any submit options embedded in the job script, and before…
reporting – Grid Engine reporting file format Description A Grid Engine system writes a reporting file to $SGE_ROOT/default/common/reporting. The reporting file contains data that can be used for accounting, monitoring and analysis purposes. It contains information about the cluster (hosts, queues, load values, consumables, etc.), about the jobs running in the cluster and about sharetree…
queue_conf – Grid Engine queue configuration file format Description This manual page describes the format of the template file for the cluster queue configuration. Via the -aq and -mq options of the command, you can add cluster queues and modify the configuration of any queue in the cluster. Any of these change operations can be…
qtask – file format of the qtask file. Description A qtask file defines which commands are submitted to Grid Engine for remote execution by The qtask file optionally may contain command-line parameters. These parameters are passed to the command being used by qtcsh to submit the commands. A cluster global qtask file defining cluster wide…
sge_qstat – xxQS_NAMExx default qstat file format Description sge_qstat defines the command line switches that will be used by qstat by default. If available, the default sge_qstat file is read and processed by There is a cluster global and a user private sge_qstat file. The user private file has the highest precedence and is followed…