29 | | The descriptor for each task includes the logical name of the application, or 'worker program'. |
30 | | If the worker program uses standard I/O (stdin, stdout or stderr) |
31 | | the descriptor specifies the logical names of the files |
32 | | to which these are to be connected. |
33 | | The descriptor may also specify command-line arguments to be passed to the worker program. |
34 | | '''wrapper''' itself may be passed command-line arguments (specified in the workunit template); |
35 | | these are passed to each of the worker programs after those specified in the job file. |
| 31 | The descriptor for each task includes: |
| 32 | |
| 33 | '''application''':: The logical name of the application, or 'worker program'. |
| 34 | '''stdin_filename''', '''stdout_filename''', '''stderr_filename''':: The logical names of the files to which stdin, stdout, and stderr are to be connected (if any). |
| 35 | '''command_line''':: command-line arguments to be passed to the worker program. '''wrapper''' itself may be passed command-line arguments (specified in the workunit template); these are passed to each of the worker programs after those specified in the job file. |
| 36 | '''weight''':: the contribution of each task to the overall fraction done is proportional to its weight (floating-point, default 1). For example, if your job has tasks A and B, and A uses 100 times more CPU time than B, set A.weight=100 and B.weight=1. |
| 37 | '''checkpoint_filename''':: the name of the checkpoint file used by the app, if any. When this is modified, the wrapper assumes that a checkpoint has been completed and notifies the core client. |