Bok,
There is no 6.2.19 or 6.2.21 left anymore in the x86_64 side at boincdl.
I would much rather download the sources and compile my own. that way I get an AMD64 scheduled version anyway.... meaning the benchmarks come out correctly, etc.
I do have my client connection value == 0. It likes that.... Now, I found something, possibly related and please verify that if you specify 100.00 (make sure to put in the .00) for your cpu utilization and loading parameters (bottom two) of the processors tab that all is still ok for you; that you don't get a stderr report from the project attached to your results. It reports errors for me... and then 'ignores' the invalid XML value of 100.00 It also ignores the invalid date.... I presume the completion date deadline (in unix time format) because it's also a float (.00000) and not an integer (which time and cpu% should be..... as in eg.100%).
I will continue to look at results and see what I can find... and perhaps we can figure out if it is my machine/client or the project ??? It has not impacted my results validity OTHER than lowering the claimed credits and artificallly raising the CPU time used. ~10,000 seconds???? these things are done in approx 2 hrs except for the P4, which does have some issues and takes about 9,000 seconds
If this is 6.2.15 related, then I understand..... and will have to find a way to get something better... even if 32 bit mode only.
As for the NFS issue.... I know that is the 'NetworkManager' package..... I have a work around by putting in manual routing statements into the table for host->host NFS connections and all is fine. Yet if you look at 'netstat -r' everything is fine there.... Again, another FC-9 error that has NEVER existed before in FC-8. I never had this problem until FC-9 came out. Perhaps it's time to switch / try something else in spite of my long standing familiarity to Suse and Redhat Linux.
(More personal + professional with Redhat, but experience with Suse at the personal level as well in the early days)....
Is is perhaps time to drop BACK to a 32 bit install for running boinc? I know that's why my benchmarks are messed up.... it was a perfect piece of algebra to compute the correct value that BOINC reported.
It does make sense for 32 bit boinc..... if this project is 32 bit based (even if 64 bit wrapped)....
Things like OGR really do benefit from 64 bit mode. Personal projects (video, audio, math, etc) and true boinc 64 bit math are fantastic in 64 bit mode. aka... anything moving data or doing real 64 bit final or interim result math, benefits. (more work / clock... plain and simple).
Advice? A 32 bit and a 64 bit install of Fedora or Suse or ????? (just not Gentoo or Ubuntu please.... <grin>)
FWIW: BOINC is the ONLY application I have trouble with in 64 bit mode other than the OS NFS glitch in the routing table
C.
here is what I got....
Code:
<core_client_version>6.2.15</core_client_version>
<![CDATA[
<stderr_txt>
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1231497971.000000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
APP: NQueen checkpoint done (6.667 %)
APP: NQueen checkpoint done (13.333 %)
APP: NQueen checkpoint done (20.000 %)
APP: NQueen checkpoint done (26.667 %)
APP: NQueen checkpoint done (33.333 %)
APP: NQueen checkpoint done (40.000 %)
APP: NQueen checkpoint done (46.667 %)
APP: NQueen checkpoint done (53.333 %)
APP: NQueen checkpoint done (60.000 %)
APP: NQueen checkpoint done (66.667 %)
APP: NQueen checkpoint done (73.333 %)
APP: NQueen checkpoint done (80.000 %)
APP: NQueen checkpoint done (86.667 %)
APP: NQueen checkpoint done (93.333 %)
</stderr_txt>
]]>