I have not been running BOINC for a while, as my CPY ran too hot during the
hot autumn and summer we have had.

Now I run it again, and off course I have overdue workunits to finish, or
abort.

They were just started - according to KBoincSpy - so I used the KBoincSpy to
abort the units. I'm running 2 threads on my P4, and they were both
aborted. New WUs were downloaded and I thought that this was it.

But when I start BOINC from CLI, I get;

006-12-16 13:04:08 [---] General prefs: no separate prefs for home; using
your defaults
2006-12-16 13:04:08 [SETI@home] Result 08jn03aa.5247.13216.922144.3.165_3 is
23.95 days overdue.
2006-12-16 13:04:08 [SETI@home] Result 08jn03aa.5247.13216.922144.3.165_3 is
23.95 days overdue.
2006-12-16 13:04:08 [SETI@home] You may not get credit for it.  Consider
aborting it.
2006-12-16 13:04:08 [SETI@home] You may not get credit for it.  Consider
aborting it.
2006-12-16 13:04:08 [---] Remote control not allowed; using loopback address
2006-12-16 13:04:08 [SETI@home] Deferring computation for result
08jn03aa.5247.13216.922144.3.165_3
2006-12-16 13:04:08 [SETI@home] Resuming computation for result
16mr99ab.29284.18912.103400.3.171_1 using setiathome_enhanced version 5.12
2006-12-16 13:04:08 [---] Insufficient work; requesting more
2006-12-16 13:04:08 [---] schedule_cpus: must schedule
2006-12-16 13:04:08 [---] Computer is overcommitted
2006-12-16 13:04:08 [---] Less than 1 day until deadline.
2006-12-16 13:04:08 [---] Deadline is before reconnect time
2006-12-16 13:04:08 [---] New work fetch policy: no work fetch allowed.
2006-12-16 13:04:08 [---] New CPU scheduler policy: earliest deadline first.
2006-12-16 13:04:08 [---] earliest deadline: 1168603045.000000
16mr99ab.29284.18912.103400.3.171_1

But according KBoincSpy the report deadline on that WU, is 12th january
2007.....?

If there is a mismatch between BOINC and KBoincSpy, how can I abort WUs from
CLI ?.

BR

Stig
-- 
* Registered Linux user #291266, with http://counter.li.org.*