Custom Query (981 matches)

It seems that when a user edits their profile this clears uotd_time, which was a record of when they were last UOTD. By the default policy this immediately makes them again eligible for UOTD.

I think it makes more sense to preserve the last uotd_time. Projects which want to alow people to be UOTD more than once can implement that policy themselves.

Here's the history: I had setup a new install of Windows XP with SP2 on an Intel Core 2 Dual 6600 (2.4ghz) system. I installed client 5.10.20 to run as a service, no interaction with the desktop. I attached the client to BAM and then from the client connected to WCG. The system processes for a while. A couple days later the boinc client had unloaded itself / crashed.

Looking at the logs it seems that BAM told the client to detach from WCG which the client did but then continues to try and cruch a work unit which is probably what lead to the crash.

I've attached the two log files which had data in them. I didn't have any debug options enabled, sorry.

Debugging checkpoint code can be hard if it requires running under the control of the core client, so it's often useful to make it checkpoint without caring about preferences when running as standalone. For example, making it checkpoint always​ if standalone (instead of calling boinc_time_to_checkpoint), but that causes too much I/O. It's much better to make it checkpoint at a fixed interval​

I suggest adding a feature inside boinc_time_to_checkpoint itself to return true every few seconds if running standalone. Maybe make it possible to change the checkpoint interval.