- client: projects with zero resource share are always lower priority,

for both job sched and work fetch,
    than projects with positive resource share.

svn path=/trunk/boinc/; revision=23946

checkin_notes

@@ -4673,7 +4673,7 @@ David  6 Aug 2011
         submit_example.php
         submit.php
 
-David  6 Aug 2011
+David  7 Aug 2011
     - remote job submission: bug fixes
 
     html/
@@ -4684,3 +4684,12 @@ David  6 Aug 2011
         user/
             submit_example.php
             submit.php
+
+David  7 Aug 2011
+	- client: projects with zero resource share are always lower priority,
+		for both job sched and work fetch,
+		than projects with positive resource share.
+
+	client/
+		cpu_sched.cpp
+		work_fetch.cpp

client/cpu_sched.cpp

@@ -608,6 +608,13 @@ void project_priority_init() {
 
 double project_priority(PROJECT* p) {
     double x = p->resource_share_frac - p->pwf.rec_temp/rec_sum;
+
+    // projects with zero resource share are always lower priority
+    // than those with positive resource share
+    //
+    if (p->resource_share == 0) {
+        x -= 1;
+    }
 #if 0
     msg_printf(p, MSG_INFO,
         "priority: rs frac %.3f rec_temp %.3f rec_sum %.3f prio %f\n",

client/work_fetch.cpp

@@ -872,7 +872,6 @@ void WORK_FETCH::compute_work_request(PROJECT* p) {
     clear_request();
     if (config.fetch_minimal_work && gstate.had_or_requested_work) return;
     if (p->dont_request_more_work) return;
-    if (p->resource_share  == 0) return;
     if (p->non_cpu_intensive) {
         if (!has_a_job(p)) {
             rsc_work_fetch[0].req_secs = 1;