It appears there is no easy way to find which version of seti i am running other than to examine completed output "results". I do see "enhanced 5.17" in boincmgr but I would rather see something like "R-2.2B|xT|FFT:IPP_SSE3|Ben-Joe" . Is there a mod that xml file that can be made so that boincmgr (or boincview) can display the client version I am using?
Could I just replace the "5.17" that is in that xml with 2.2b_SSE3 identifier?
..thanks..
I have a bunch of systems and found that by the time I got the last one upgraded the first one was sometimes running old software.
...
Is there any problem with replaceing "setiathome_enhanced" with, for example, "seti_enh_2200_SSE2" ?
...
I have a bunch of systems and found that by the time I got the last one upgraded the first one was sometimes running old software.
I have some 40+ linux machines and suffer also from this.
to get around it, I wrote a script that can enquire of various thigs on each host
for example glibc version, chicken version, kernel version etc
Anyway, if I was able to boot all of my "retired" dual p3's with a cd linux I would be interested in your script. Every now and then we build a huge rack of systems and they need to be burned in like these dual 64 bit athlons http://tinyurl.com/qpbow They sat idle for months, they were diskless except for a cd and would have made a good seti farm.
It appears there is no easy way to find which version of seti i am running other than to examine completed output "results". I do see "enhanced 5.17" in boincmgr but I would rather see something like "R-2.2B|xT|FFT:IPP_SSE3|Ben-Joe" . Is there a mod that xml file that can be made so that boincmgr (or boincview) can display the client version I am using?
Could I just replace the "5.17" that is in that xml with 2.2b_SSE3 identifier?
<app_info>
<app>
<name>seti_enhanced</name>
<user_friendly_name>Seti 5.17 R-2.2B|xT|FFT:IPP_SSE2|Ben-Joe</user_friendly_name>
</app>
<file_info>
<name>KWSN_2.2B_SSE2-P4_Ben-Joe.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>seti_enhanced</app_name>
<version_num>517</version_num>
<file_ref>
<file_name>KWSN_2.2B_SSE2-P4_Ben-Joe.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
...Anyway, seems like a worthwhile change. Do you know what minimum version of BOINC is needed to use the <user_friendly_name> XML field? Also, will older versions just silently ignore it or die?
Tested it on BOINC 5.4.9 and 5.8.15, both don't complain
| SETI@home Beta Test | - Seti 5.15 R-2.2B|xB+GFX|FFT:IPP_SSE2|Ben-Joe 5.17 |
| SETI@home | - Seti 5.15 R-2.2B|xB+GFX|FFT:IPP_SSE2|Ben-Joe 5.15 |
And now :P my BoincView 1.5.0 beta8 shows:
SETI@home Beta Test - Seti 5.15 R-2.2B|xB+GFX|FFT:IPP_SSE2|Ben-Joe 5.17 SETI@home - Seti 5.15 R-2.2B|xB+GFX|FFT:IPP_SSE2|Ben-Joe 5.15
That's a known feature of BOINC CC ... It used to be far worse as CC was not able to distinguish between identically named applications for two different projects (SETI and SETIbeta). When an user introduced app_info.xml for say SETI, then SETIbeta started to crash because it had a bit higher version number.
I do remember the feature, I was immediately using the then-newer Boinc aplhas. But as I understood Joe's related changes from many months ago, the issue should be really away. And, BoincManager does not suffer from it... :-\
[edit]How to take a look at the GUI RPC data flow? It's a local client, so Wireshark is useless, and I'd have to make the authentication manually, if connected over telnet...[/edit]
How to take a look at the GUI RPC data flow? It's a local client, so Wireshark is useless...
I don't know if this would really work (and how to do it) in Windows, but how about running ethereal (or some other packet sniffing tool) against loopback device?
I'd just like to point out that with BOINC core client version 5.9.X (and presumably all the newer ones), that introduces mechanism of alternative platforms, one has to modify app_info.xml.
- core client: when parse app_info.xml, set platform to primary platform. Otherwise anonymous platform mechanism doesn't work.