| 1 | = Single jobs = |
| 2 | |
| 3 | BOINC is designed to handle streams of millions of jobs. |
| 4 | However, you can also submit single jobs for remote execution. |
| 5 | To do this, configure your BOINC server to handle single jobs (see below). |
| 6 | Then type |
| 7 | {{{ |
| 8 | boinc_job [boinc-options] program [program-options] |
| 9 | }}} |
| 10 | The boinc-options are: |
| 11 | |
| 12 | '''--infile name''':: specifies an input file. |
| 13 | '''--stdin name''':: direct the given file to the program's stdin. |
| 14 | '''--outfile name''':: specifies an output file. |
| 15 | '''--stdout name''':: the program's stdout will be directed to the given file. |
| 16 | '''--platform''':: the program is to be run on the given [[BoincPlatform platform]] (default: i686-pc-linux-gnu). |
| 17 | |
| 18 | You can include as many --infile and --outfile options as you want, |
| 19 | and at most one of others. |
| 20 | |
| 21 | The '''program-options''' will be passed as command-line arguments to the program |
| 22 | when it runs on the remote machine. |
| 23 | |
| 24 | If the program requires any non-standard libraries, it should link these statically. |
| 25 | Otherwise it will fail to run on machines that lack these libraries. |
| 26 | |
| 27 | When the job is completed successfully, the output files will appear in the job directory. |
| 28 | |
| 29 | == Configuring BOINC for single jobs == |
| 30 | |
| 31 | Add the following to your project.xml file: |
| 32 | {{{ |
| 33 | <app> |
| 34 | <name>single_job_i686-pc-linux-gnu</name> |
| 35 | <user_friendly_name>Single jobs for Linux</user_friendly_name> |
| 36 | </app> |
| 37 | }}} |
| 38 | and run [ToolsXadd xadd]. |