Hi,

I'm running Linux Lite, which is Ubuntu 14.04 based.
I have BOINC 7.2.42 which works O.K with SETI, MW@H.

With moowrap results just sit there "Ready To Report" until I do a "manual" update

Any ideas, I've looked in computer preferences & settings,
and unless I've missed something..??
I don't see why it's not returning results automatically.

Thanks... Dave

Hi,

I'm running Linux Lite, which is Ubuntu 14.04 based.
I have BOINC 7.2.42 which works O.K with SETI, MW@H.

With moowrap results just sit there "Ready To Report" until I do a "manual" update

Any ideas, I've looked in computer preferences & settings,
and unless I've missed something..??
I don't see why it's not returning results automatically.

Thanks... Dave

You need to make a cc_config.xml file like this:

<<cc_config>>
<options>
<report_results_immediately>1</report_results_immediately>
</options>
</cc_config>

I have no idea in Linux where it goes but in Windows it goes in the C:\program data\Boinc directory. Also in Windows you must NOT use a word processing program, you use NOTEPAD as WP programs add stuff that Boinc can't read, making the file unusable.

After the file is in place tell Boinc to read the config files and you should be good to go.

An alternative is to just let Boinc handle all communications on its own, I think you are being too pro-active in your need for more units. Boinc sends back the completed units and gets new units all at the same time, so if you still have units being crunched on Boinc won't be in too much of a hurry to refill the cache.

Hi mikey,

Thanks for the info, appreciated.

I appear to have the cc_config.xml in 2 locations.
Will need to figure out which is used, possibly by access date/time.

It's not that I want the results any faster.
With SETI@H & MW@H they just seem to return the results more frequently.

Thanks... Dave

With moowrap results just sit there "Ready To Report" until I do a "manual" update

Reporting any uploaded results is decided solely by the BOINC Client, neither our apps nor our scheduler have anything to say about the matter.

How long have you given the BOINC Client to decide it wants to report our tasks and get new ones? Which of your hosts is affected or are they all behaving similarly?

If you have long queue of work, it can take a while but it should eventually decide to do it unless there's a bug. Also, any uploads pending or are these task really ready? It's also possible for BOINC Client to postpone reporting if additional tasks are ready soon.

Anything relevant in BOINC Client event logs related to our project regarding decisions on doing a scheduler request? You might need to add some debug flags to see more info.

If you can, you can try updating to a version in the 7.4 branch as there has been various changes in different BOINC Client version on when and why to make a scheduler request. However, things should work with 7.2.42 too so it's not mandatory to update.

-w

Hi mikey,

Thanks for the info, appreciated.

I appear to have the cc_config.xml in 2 locations.
Will need to figure out which is used, possibly by access date/time.

The one in the c:\program data\Boinc location is the one used mostly and where this should go, the one inside the project folder is ONLY for that project.

It's not that I want the results any faster.
With SETI@H & MW@H they just seem to return the results more frequently.

Thanks... Dave

You will NOT get credits any faster than the project can process them, there is normally about a 2 to 3 week lag time at each project before your credits will even out and you will stop climbing. Most projects have 'wingmen', that means it takes both of you retuning similar results, that are within the pre-predicted expected range, before anyone gets any credits. At Moo however they do not use 'wingmen', so it is just you returning your results and you aren't waiting on someone else, that tends to make things faster.