Changes between Version 32 and Version 33 of ProjectOptions

Timestamp:

Jul 16, 2007, 4:40:32 PM (17 years ago)

Author:

Nicolas

Comment:

Fixed link

ProjectOptions

@@ -54 +54 @@
         This element only has an effect when used in conjunction with the previous locality scheduling element. It tells the scheduler to use 'trigger files' to inform the project that more work is needed for specific files. The period is the number of seconds which the scheduler will wait to see if the project can create additional work. Together with project-specific daemons or scripts this can be used for 'just-in-time' workunit creation. See [LocalityScheduling Locality Scheduling].
  '''min_core_client_version'''::
-        If the scheduler gets a request from a client with a version number less than this, it returns an error message and doesn't do any other processing.  The version number is expressed as an integer with the encoding major*100+minor.  You can also specify this separately for each [BoincApps application].
+        If the scheduler gets a request from a client with a version number less than this, it returns an error message and doesn't do any other processing.  The version number is expressed as an integer with the encoding major*100+minor.  You can also specify this separately for each [AppVersion application].
  '''choose_download_url_by_timezone'''::
         When the scheduler sends work to hosts, it replaces the download URL appearing in the data and executable file descriptions with the download URL closest to the host's timezone. The project must provide a two-column file called 'download_servers' in the project root directory. This is a list of all download servers that will be inserted when work is sent to hosts. The first column is an integer listing the server's offset in seconds from UTC. The second column is the server URL in the format such as !http://einstein.phys.uwm.edu. The download servers must have identical file hierarchies and contents, and the path to file and executables must start with '/download/...' as in '!http://X/download/123/some_file_name'.
@@ -69 +69 @@
         If set, and the client is processing a result for a WU that has been cancelled or is not in the DB (i.e. there's no chance of getting credit) send <result_abort>. If client is processing a result for a WU that has been assimilated or is overdue (i.e. there's a chance of not getting credit) send <result_abort_if_not_started>. Note: this will increase the load on your DB server.
  '''default_disk_max_used_gb'''::
-        Sets the default value for the disk_max_used_gb preference so it's consistent between the scheduler and web pages. The scheduler uses it when a request for work doesn't include preferences, or the preference is set to zero. The web page scripts use it to set the initial value when displaying or editing preferences the first time, or when the user never saved them. Default is 100.
+        Sets the default value for the `disk_max_used_gb` preference so it's consistent between the scheduler and web pages. The scheduler uses it when a request for work doesn't include preferences, or the preference is set to zero. The web page scripts use it to set the initial value when displaying or editing preferences the first time, or when the user never saved them. Default is 100.
  '''default_disk_max_used_pct'''::
-        Sets the default value for the disk_max_used_pct preference so its consistent between the scheduler and web pages. The scheduler uses it when a request for work doesn't include preferences, or the preference is set to zero. The web page scripts use it to set the initial value when displaying or editing preferences the first time, or when the user never saved them. Default is 50.
+        Sets the default value for the `disk_max_used_pct` preference so its consistent between the scheduler and web pages. The scheduler uses it when a request for work doesn't include preferences, or the preference is set to zero. The web page scripts use it to set the initial value when displaying or editing preferences the first time, or when the user never saved them. Default is 50.
  '''default_disk_min_free_gb'''::
-        Sets the default value for the disk_min_free_gb preference so its consistent between the scheduler and web pages. The scheduler uses it when a request for work doesn't include preferences. The web page scripts use it to set the initial value when displaying or editing preferences the first time, or when the user never saved them. Also, the scheduler uses this setting to override any smaller preference from the host, it enforces a 'minimum free disk space' to keep from filling up the drive. Recommend setting this no smaller than .001 (1MB or 1,000,000 bytes). Default is .001.
+        Sets the default value for the `disk_min_free_gb` preference so its consistent between the scheduler and web pages. The scheduler uses it when a request for work doesn't include preferences. The web page scripts use it to set the initial value when displaying or editing preferences the first time, or when the user never saved them. Also, the scheduler uses this setting to override any smaller preference from the host, it enforces a 'minimum free disk space' to keep from filling up the drive. Recommend setting this no smaller than .001 (1MB or 1,000,000 bytes). Default is .001.
  '''reliable_min_avg_credit, reliable_min_avg_turnaround'''::
-        Hosts for which expavg_credit/ncpus is at least reliable_min_avg_credit and whose average turnaround is at most reliable_max_avg_turnaround are considered 'reliable'.
+        Hosts for which `expavg_credit`/`ncpus` is at least `reliable_min_avg_credit` and whose average turnaround is at most reliable_max_avg_turnaround are considered 'reliable'.
  '''reliable_time, reliable_reduced_delay_bound'''::
         When the age of a workunit exceeds reliable_time (typically 2-3X the delay bound), send results only to reliable hosts, and multiply the delay bound by reliable_reduced_delay_bound (typically 0.5 or so).