| 32 | |
| 33 | == Running your own application == |
| 34 | |
| 35 | Suppose that instead of the sample application, you want to run your own. |
| 36 | Logged in to the virtual server, type |
| 37 | {{{ |
| 38 | cd ~/projects/test |
| 39 | html/ops/single_job_setup.php ~/boinc_samples |
| 40 | }}} |
| 41 | and follow the resulting instructions. |
| 42 | This configures your project to handle "single job" submissions. |
| 43 | Then compile a program in your home directory. |
| 44 | Say the program is '''a.out''' and that it writes to stdout. |
| 45 | Then, in your home directory, type |
| 46 | {{{ |
| 47 | boinc/tools/boinc_submit --stdout foo a.out |
| 48 | }}} |
| 49 | When this completes, '''foo''' will contain the output of a.out, |
| 50 | run on one of the BOINC client hosts. |
| 51 | |
| 52 | == What's next? == |
| 53 | |
| 54 | This demonstrates how you can use BOINC to run programs remotely, |
| 55 | but it's not the complete picture. |
| 56 | In particular: |
| 57 | |
| 58 | * This demo uses only Linux clients. BOINC lets you use heterogeneous pools of Windows, Mac OS X, Linux, and other clients. |
| 59 | * This demo involves manual submission of single jobs. BOINC lets you create automated systems that create and handle millions of jobs per day. |
| 60 | * In this demo, we trust the client to return correct results. BOINC lets you set things up so that results from faulty or malicious clients are automatically detected and rejected. |
| 61 | |
| 62 | ... and many, many other things. |
| 63 | Keep on reading. |