Search
Page 5 of 23. Showing 226 results (0.013 seconds)
qbshove
-evaluates all jobs. Repeatedly running qbshove will only increase the load on your Supervisor, possibly resulting in diminished performance. Usage qbshove [options] jobID… | 0…qbtop
relative to other jobs having the same priority. Usage qbtop [options] jobID… | 0 where JobID is one or more job IDs, and 0 is a wild card token representing all the user's jobs…qbblock
or more job IDs, and 0 is a wild card token representing all the user's jobs. Options Option Description --work Block work (default: on) --subjob Block…qbinterrupt
is a wild card token representing all the user's jobs. Options Option Description --running Interrupt running jobs --pending Interrupt pending jobs…qbkill
, and 0 is a wild card token representing all the user's jobs. Options Option Description --work Kill work (default: on) --subjob Kill subjobs (default…How to use qbwrk.conf
] is reserved for assignment to all nodes Copy below and alter for your environment [Farm] proxy_execution_mode = user worker_properties = host.nuke6.2=1, host.maya2011=1 worker_cpus…supervisor_manifest
Synopsis supervisor_manifest = path path were the manifest log is located. This log contains all events concerning jobs and their actions. The format is similar to the job…proxy_account
Synopsis proxy_account = user This is only to be specified if the administrator wants all jobs to be run under the single user account. By default, all jobs are run…qbhist
where JobID is one or more job IDs, and 0 is a wild card token representing all the user's jobs. Options Option Description --xml Output in XML format --help…qblock
… where hostname is the name of the host to be locked. It can be followed by 0 or more hostnames. Options Switch Description --all lock all hosts --down lock…