Less than 1 day until deadline.
From Unofficial BOINC Wiki
Message Type: Information Message
In order to ensure that work is completed before Result Deadlines, if there is less than 1 day to the Result Deadline for a Result and that Result is not completed, the CPU Scheduler will enter Earliest Deadline First mode.
This message is now a debugging message and will not show up in the BOINC Versions past 4.45, unless it is reclassified at a later date.
 Example Log(s)
 Deadline Is Before Reconnect Time
2005-06-09 06:19:42 [ ] schedule_cpus: must schedule 2005-06-09 06:19:42 [ ] Less than 1 day until deadline. 2005-06-09 06:19:42 [ ] Deadline is before reconnect time 2005-06-09 06:19:42 [ ] New CPU scheduler policy: earliest deadline first. 2005-06-09 06:19:42 [ ] earliest deadline: 1118882043.000000 h0010A_1_82923_1 2005-06-09 07:07:35 [ ] request_reschedule_cpus: process exited 2005-06-09 07:07:35 [ProteinPredictorAtHome] Computation for result h0010A_1_82923_1 finished 2005-06-09 07:07:35 [ ] schedule_cpus: must schedule 2005-06-09 07:07:35 [ ] earliest deadline: 1118885075.000000 h0010A_1_83365_1 2005-06-09 07:07:35 [ProteinPredictorAtHome] Starting result h0010A_1_83365_1 using mfoldB125 version 4.29 2005-06-09 07:07:36 [ProteinPredictorAtHome] Started upload of h0010A_1_82923_1_0 2005-06-09 07:07:36 [ProteinPredictorAtHome] Started upload of h0010A_1_82923_1_1 2005-06-09 07:07:38 [ProteinPredictorAtHome] Finished upload of h0010A_1_82923_1_0 2005-06-09 07:07:38 [ProteinPredictorAtHome] Throughput 24184 bytes/sec 2005-06-09 07:07:38 [ProteinPredictorAtHome] Finished upload of h0010A_1_82923_1_1 2005-06-09 07:07:38 [ProteinPredictorAtHome] Throughput 764330 bytes/sec 2005-06-09 07:07:38 [ProteinPredictorAtHome] Started upload of h0010A_1_82923_1_2 2005-06-09 07:07:40 [ProteinPredictorAtHome] Finished upload of h0010A_1_82923_1_2 2005-06-09 07:07:40 [ProteinPredictorAtHome] Throughput 41864 bytes/sec
- Because this is a debugging message, I am not giving the log the usual line-by-line treatment. Yell at me if you don't like it.
There was an event that required the CPU Scheduler to make a change in processing priorities. In this case, it first determined that there was the possibility of problems with making the scheduled Result Deadlines.
With that determination, it located the Result with the largest problem and scheduled that Result for processing (h0010A_1_82923_1). Not quite an hour later, the Result is done triggering another scheduling event where the next Result is selected (h0010A_1_83365_1).
As that is started, the remaining line show that there are several Result Data Files to be uploaded and they were processed, though there was some interlacing because each file is handled independently of the others so, the log is a little odd here ... but nothing to worry about.
 Related Messages
 Work Scheduler Messages (General)
- request_reschedule_cpus: exit_tasks
- request_reschedule_cpus: files downloaded
- request_reschedule_cpus: process exited
- request_reschedule_cpus: project op
- request_reschedule_cpus: Resuming activities
- request_reschedule_cpus: start failed
- schedule_cpus: time '(x.y)'