Hi,
I use my 7gb of peak/active bandwidth for work and do not appreciate Leiden downloading new projects during that peak/active bandwidth period and have my preferences set to limit that (downloads allowed between 00:10 - 11:50 GMT+10 - my off-peak period). Tonight I have seen not only Leiden, but, also Milkyway & Spinhenge download new projects during this peak period. I have disconnected from Spinhenge completely as they would not let me logon to object to their interinference with my broadband.
I use my peak broadband for WORK.... Not for a bunch of boffins to bump up their processing.
16/06/2010 7:42:59 PM Leiden Classical Started download of cu111leps_trajtou.inp_BIG_80398718_1270105678_180565
16/06/2010 7:43:01 PM Leiden Classical Finished download of cu111leps_trajtou.inp_BIG_80398718_1270105678_180565
If this continues to happen from your institute, I will regretably disconnect from this project. The ability for me to earn a wage to pay for my mortgage comes before donating my spare processing power for university use.
/ 
- 
That was a whole whopping 2 seconds of your precious bandwith........If that interferes with your mortgage you might considering quitting BOINC altogether.
____________
/ - That was a whole whopping 2 seconds of your precious bandwith........If that interferes with your mortgage you might considering quitting BOINC altogether.
I also think that you should complain at BOINC, rather than at the project(s). Either the timeframe you set does not work -that is a fault in the BOINC client-, or it does not take into account the fact that there are different timezones around the world -that is also a fault in the BOINC client-.
____________
/ - 
Forum moderator
Project administrator
Project developer
Project tester
Volunteer developer
Volunteer tester
Project scientist
private message
Joined: Nov 14, 2005
Posts: 630
ID: 1
Credit: 1,417,572
RAC: 2
I do not understand the precise issue.
m.
____________
M.F. Somers
/ - I do not understand the precise issue.
m.
I do, David got a new project at a time he had specified *NOT* to receive any BOINC-related stuff, during his working hours. I already pointed out that
1. it had cost him only 2 seconds, and that
2. he is barking up the wrong tree, he should take it up with the BOINC-client developpers.
____________
/ - I do not understand the precise issue.
m.
I'm afraid that there is more to David's complaint than I originally thought. I am even afraid that he was right from the start: it is actually the Leiden application that is at fault.
You can set your preferences for BOINC using Advanced - Local Preferences (Geavanceerd - Lokale voorkeuren) in the BOINC Client, resulting in the global_prefs_override.xml file in the C:\ProgramData\BOINC directory (when using Windows 7, Windows server 2003/2008)
You can set specific preferences for the Leiden application by logging into your account and specifying them, resulting in the global_prefs.xml file in the C:\ProgramData\BOINC directory (when using Windows 7, Windows server 2003/2008)
And what do I see to my horror when analysing my results:
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
Unrecognized XML in parse_init_data_file: hostid
Skipping: 79083
Skipping: /hostid
Unrecognized XML in parse_init_data_file: starting_elapsed_time
Skipping: 0.000000
Skipping: /starting_elapsed_time
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1285091548.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: run_gpu_if_user_active
Skipping: 1
Skipping: /run_gpu_if_user_active
Unrecognized XML in GLOBAL_PREFS::parse_override: suspend_cpu_usage
Skipping: 0.000000
Skipping: /suspend_cpu_usage
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
Unrecognized XML in GLOBAL_PREFS::parse_override: daily_xfer_limit_mb
Skipping: 0.000000
Skipping: /daily_xfer_limit_mb
Unrecognized XML in GLOBAL_PREFS::parse_override: daily_xfer_period_days
Skipping: 0
Skipping: /daily_xfer_period_days
Unrecognized XML in parse_init_data_file: hostid
Skipping: 79083
Skipping: /hostid
Unrecognized XML in parse_init_data_file: starting_elapsed_time
Skipping: 3662.730434
Skipping: /starting_elapsed_time
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1285091548.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: run_gpu_if_user_active
Skipping: 1
Skipping: /run_gpu_if_user_active
Unrecognized XML in GLOBAL_PREFS::parse_override: suspend_cpu_usage
Skipping: 0.000000
Skipping: /suspend_cpu_usage
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
Unrecognized XML in GLOBAL_PREFS::parse_override: daily_xfer_limit_mb
Skipping: 0.000000
Skipping: /daily_xfer_limit_mb
Unrecognized XML in GLOBAL_PREFS::parse_override: daily_xfer_period_days
Skipping: 0
Skipping: /daily_xfer_period_days
</stderr_txt>
]]>
The Leiden application seems to blissfully ignore the settings as specified in the global_prefs_override.xml/global_prefs.xml files, including those that state when the network is to be used, claiming "Unrecognized XML" and skipping the settings!
____________
/ - Forum moderator
Project administrator
Project developer
Project tester
Volunteer developer
Volunteer tester
Project scientist
private message
Joined: Nov 14, 2005
Posts: 630
ID: 1
Credit: 1,417,572
RAC: 2
I think it is a slightly more complicated issue; the scientific applications in boinc do not deal with settings or stuff like that; that's what the boinc client manager is supposed to do. In the BOINC API available for the science code no hooks are available related to any of these things. If you think about it, that makes sense; you do not want projects to recompile / retest their scientific apps every time BOINC adds a new feature into the client manager ;-). Your client manager should deal with the scheduling / download etc. and it does as far as I understand the BOINC architecture. None the less, the scientific (aka the Leiden Classical project) application are linked to a BOINC library which offers a routine to retrieve some info form the client manager configuration. This is needed in our app to set the correct random nr seed for the trajectories. For that a routine that is available in the BOINC application API is used. Now it could be that you use a newer BOINC client manger (which stores plenty of new options in its config obviously) and that the older BOINC library to which the app was linked does not recognize some of the tags. It should just ignore them in that case and it does so too, but it will also mention this in the stderr. So the messages you see are probably related to you running a newer BOINC client manager than the BOINC library we used to make the application.
m.
____________
M.F. Somers
/ - 
Now it could be that you use a newer BOINC client manger (which stores plenty of new options in its config obviously) and that the older BOINC library to which the app was linked does not recognize some of the tags. It should just ignore them in that case and it does so too, but it will also mention this in the stderr. So the messages you see are probably related to you running a newer BOINC client manager than the BOINC library we used to make the application.
Yup, completely correct.
If David has any problems with preferences not being followed, it's an effect of the BOINC client. I see he's using 6.10.18, which was a development version. Perhaps it's time for him to update to the recommended release version 6.10.58
He can then also use the preferences to set the maximum amount of megabytes he wants to allow per day to be used by BOINC. Although Leiden isn't updated on server version to use that from the preferences, I see he's attached to enough projects which do allow him to use those preferences. They're global.
____________
Jord
BOINC FAQ Service
/ -