Changes between Version 83 and Version 84 of WrapperApp

Timestamp:

Feb 21, 2014, 2:41:09 PM (11 years ago)

Author:

Juha

Comment:

fix link to input template

WrapperApp

@@ -83 +83 @@
  '''setenv''':: Environmental variable needed for the applications run-time environment - you can have more than one <setenv> entry, use the VARNAME=VAR_VALUE form, e.g. LD_LIBRARY_PATH=$PROJECT_DIR:$LD_LIBRARY_PATH.  You can also use the $NTHREADS macro if you have an environment variable that needs the number of threads or processes to launch.
  '''daemon''':: Denotes that this task is a 'daemon' process that should run in the background asynchronously while the other tasks are run sequentially.  The wrapper will shut down this daemon when the last task has exited
- '''append_cmdline_args''':: if set, the wrapper's command-line arguments (specified in the [WorkGeneration#templates input template]) are passed to the worker program, after those in <command_line>.
- '''time_limit''':: if given, kill the task after the given amount of elapsed (running) time.  Note: on Windows, tasks are killed using TerminateProcess(), which doesn't flush stdio buffers; take this into account.
+ '''append_cmdline_args''':: if set, the wrapper's command-line arguments (specified in the [JobTemplates#Inputtemplates input template]) are passed to the worker program, after those in <command_line>.
+ '''time_limit''':: if given, kill the task after the given amount of elapsed (running) time.  Note: on Windows, tasks are killed using !TerminateProcess(), which doesn't flush stdio buffers; take this into account.
 
 The job file can specify multiple tasks.