diff --git a/doc/backend_work_sequence.php b/doc/backend_work_sequence.php deleted file mode 100644 index 7ddd1eba45..0000000000 --- a/doc/backend_work_sequence.php +++ /dev/null @@ -1,32 +0,0 @@ - -Project that use work sequences will need two additional processes: -

- - - - - - - - - - - - - - - - -
ComponentBOINC-supplied partproject-supplied part
Work sequence relocater: -detects work sequences whose hosts have failed, -and relocates them to other hosts.A program seq_relocateSome parameters used by seq_relocate
Work sequence validation and accounting: -Similar to result validation, but for work sequences. -A program seq_validateAn application-specific function, -linked with seq_validate, that compares sets of redundant results.
-"; -page_tail(); -?> diff --git a/doc/batch.php b/doc/batch.php deleted file mode 100644 index 76cf236ea7..0000000000 --- a/doc/batch.php +++ /dev/null @@ -1,15 +0,0 @@ - -Workunits and results can be grouped together into batches. -Each batch is represented by an integer. -Results must belong to the same batch as their workunit. -

-BOINC provides tools for manipulating workunits and results by -batch: e.g., for changing the status of all results in a batch from -'inactive' to 'unsent'. -"; -page_tail(); -?> diff --git a/doc/bugs.php b/doc/bugs.php deleted file mode 100644 index 400e545939..0000000000 --- a/doc/bugs.php +++ /dev/null @@ -1,31 +0,0 @@ - - -

  • Post a message to the appropriate -email list. -Do this first. -Your bug may have already been fixed. - -
  • Use BOINC's -external bug database -(which is readable and writable). - -"; -if (1) { - echo " -
  • Read BOINC's -internal bug database. -This is used by BOINC developers, -and is readable by the rest of the world. - -"; -} -page_tail(); -?> diff --git a/doc/busy_work.php b/doc/busy_work.php deleted file mode 100644 index 3597736e4b..0000000000 --- a/doc/busy_work.php +++ /dev/null @@ -1,34 +0,0 @@ - -The daemon program -
    -make_work -wu_name name [-wu_name name2 ... ] -cushion N
    -
    -creates copies of the given workunits (cyclically) -as needed to maintain a supply of at least N unsent results. -This is useful for testing purposes. -

    -Note: if you run the file_deleter and/or db_purge, -the master workunit or its input files may be deleted -(which will cause make_work to fail). -To avoid this, give the master workunit a name that contains -'nodelete' as a substring. -This causes the file_deleter and db_purge to skip over it. - -

    -It may be convenient to have a script that recreates the master workunit. -For example: - -

    -cp test_workunits/12ja04aa `bin/dir_hier_path 12ja04aa`
    -bin/create_work -appname setiathome -wu_name sah_nodelete -wu_template templates/setiathome_wu_0 -result_template templates/setiathome_result_0 12ja04aa
    -
    - -"; - -page_tail(); -?> diff --git a/doc/client_mac.php b/doc/client_mac.php deleted file mode 100644 index 9b6a5734c7..0000000000 --- a/doc/client_mac.php +++ /dev/null @@ -1,62 +0,0 @@ - -

    Installing BOINC on Mac OS/X

    -

    -The Mac OS X client will unpack correctly with gunzip on Mac OS X -10.2 (jaguar) or 10.3 (panther) as long as you type the command -within Terminal. Stuffit 7.x or newer will work under the Finder -in either OS X or OS 9, but I'd recommend using 'gunzip' or 'gzip -d' -within Terminal instead. - -

    -However, the two main browsers on OS X (IE 5.2.x and Safari 1.x) will -automatically unpack downloads by default, so your work may already -be done. - -

    -If you use IE, the boinc client will download and automatically unpack -leaving two files: -

      -
    1. - boinc_2.12_powerpc-apple-darwin - [this will have the stuffit icon in the finder] - -
    2. - boinc_2.12_powerpc-apple-darwin7.0.0 - [this will not have any icon in the finder] - -
    -

    - #2 is the unpacked program ready-to-run. You can just start Terminal - and run boinc. - -

    -If you use Safari, the boinc client will download and automatically -unpack, leaving a single file: -

    - This is the unpacked program, but it's not yet ready-to-run (this is - a bug with how Safari handles gzipped downloads; we'll fix this soon). - -

    - Here's what you have to do to fix the Safari download (apologies if - you already know how to do this): - -

    - Now you can run BOINC. - "; -page_tail(); -?> diff --git a/doc/client_sched.php b/doc/client_sched.php index 83da57b0d0..55faec0771 100644 --- a/doc/client_sched.php +++ b/doc/client_sched.php @@ -1,10 +1,10 @@
  • CPU scheduling policy: what result to run when. diff --git a/doc/compile.php b/doc/compile.php deleted file mode 100644 index 0fe745e96c..0000000000 --- a/doc/compile.php +++ /dev/null @@ -1,32 +0,0 @@ -Basics - - -

    Platform-specific cookbooks

    - - -

    Other information

    - -"; -page_tail(); - -?> diff --git a/doc/impl_notes.php b/doc/impl_notes.php deleted file mode 100644 index 16ec2bddce..0000000000 --- a/doc/impl_notes.php +++ /dev/null @@ -1,66 +0,0 @@ -Client - -

    Server programs

    - - -

    Protocols

    - -

    Client extensions

    - -

    Web-based extensions (statistics and account management)

    - -

    Miscellaneous

    - - -"; - -page_tail(); -?> diff --git a/doc/sched_policy.php b/doc/sched_policy.php deleted file mode 100644 index 1fdf1cf12d..0000000000 --- a/doc/sched_policy.php +++ /dev/null @@ -1,32 +0,0 @@ - -The scheduling server will attempt to send enough work to exceed a -hosts high water mark. If the amount of work the scheduling server is -sending exceeds a certain level (default is four weeks), the -scheduling server will not attach more work to a scheduler reply. -This does not prevent the scheduling server from sending a lengthy -workunit, but rather from sending multiple lengthy workunits. -

    -If a work unit uses more disk resources than a host has available, the -scheduling server will not attach that work unit. -

    -The scheduling server -estimates the amount of time a work unit will take to complete with the -formula (number of flops)/(flops per second)+(number of iops)/(iops -per second). -The number of floating point and integer operations are provided by -the project when creating the work unit, and the host calculation -speeds are included in a scheduler request. -

    -If no work is available, -or if the host cannot accept it for whatever reason -(too slow, not enough space, etc), -the scheduling server sends the message -no work available, -and requests that the client wait before sending another request. -"; -page_tail(); -?> diff --git a/doc/service.php b/doc/service.php deleted file mode 100644 index 5403e2a74c..0000000000 --- a/doc/service.php +++ /dev/null @@ -1,41 +0,0 @@ - -BOINC can be run as a Windows service. -This requires the command-line interface (CLI) version of the core client, -which is not available for download; -you'll have to build it from the source code -using Visual Studio .Net. - -

    -If you haven't already run BOINC on the machine, -you'll need to run through the setup procedure -(using either the CLI or the GUI client) -in order to establish the -account* files which are needed for the project URLs and authenticators. -

    -Then put the CLI executable (boinc_cli.exe) into the BOINC folder. -Type this from the commandline: - -

    -boinc_cli -install
    -
    - -This will setup BOINC as a Windows service which can be started on boot -and will be hidden from view. -If you are executing this on a Windows 2003 machine -the default user account that is chosen is 'Network -Service' which means you'll need to grant Read/Write/Execute/Delete permissions -to the client folder and all of its children before attempting to start -the service. -On Windows XP and older systems the client currently sets -itself up as local system. -

    -Messages are logged to the 'eventlog' - check there -periodically for error and status messages. - -"; -page_tail(); -?> diff --git a/doc/stats_sites.php b/doc/stats_sites.php deleted file mode 100644 index 960c994605..0000000000 --- a/doc/stats_sites.php +++ /dev/null @@ -1,20 +0,0 @@ -The following web sites show statistics for one or more BOINC projects: -"; -shuffle($stats_sites); -site_list($stats_sites); -echo " -These sites use XML-format data exported by BOINC projects. -The format is described -here. -If you are interested in running your own site or -participating in the development efforts, -please contact the people listed above. - -

    Statistics signature images

    -

    -The following sites offer dynamically-generated -images showing your statistics in BOINC projects. -Use these in your email or message-board signature. -"; -shuffle($sig_sites); -site_list($sig_sites); diff --git a/doc/test_client.php b/doc/test_client.php deleted file mode 100644 index 7bc9fa2a09..0000000000 --- a/doc/test_client.php +++ /dev/null @@ -1,25 +0,0 @@ -The following tests are meant for the single-user installation scenario: -

      -
    1. Attach to a project. -
    2. Schedule an RPC to the project server requesting results to process. -
    3. Download the project executable and support files. -
    4. Download a result and support files. -
    5. Begin execution of the project executable using the retrieved result and support files. -
    6. Complete a result and upload the resulting file(s) of the result execution. -
    7. Accept the update GUI RPC to tell the client to report the completed result to the scheduler. -
    8. Server Scheduler Exponential Back-off on connection failure. -
    9. File download Exponential Back-off on transient connection failure. -
    10. Server Scheduler Back-off with a requested value. -
    11. Server Scheduler error message reported to client. -
    12. File download resumes after back-off completes. -
    13. File upload resumes after back-off completes. -

    - -"; -page_tail(); -?>