| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have a small app that checks a time server on the internet (clock.psu.edu:123) and syncs the time on one computer every 2 hours. Today something happened and it set the date to Jan 2032, then 2 hours later set it back to the correct time. I understand BOINC failing to fetch work when the date went beyond the website cert expiration date, but when the time was corrected it went to
----------------------------------------Suspending computation - running CPU benchmarks and never came back from that... I found it like that about 3 hours later and had to restart BOINC to get it to start crunching again. I've disabled the time app and will sync the time manually when I see it's off... just wondered why BOINC would go into the benchmarks check and never finish (well, not finish them within 3+ hours, anyway). [Edit 1 times, last edit by Former Member at Apr 27, 2009 7:55:25 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You need to use proper time synchronisation software. No reasonable NTP client will make a large time correction. Most will only make corrections that are less than one day.
When the time is changed by a large amount, all of BOINC's time estimation is invalidated. |
||
|
|
|