I'm updating the assimilator/validator tonight, so work might be a bit scarce.

To do the dynamic checking of results (and to be able to award credit only to correct results), I've had to merge the assimilator/validator, so it might be a bit flakey until i get things worked out.

---

It needs a good kicking. 353k+ results.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

It needs a good kicking. 353k+ results.

Yeah, I noticed a bug in it where it wasn't properly assimilating results... so they built up over the last day or two. It's chugging through them right now :P

---

Noticed you are going to be updated tonight, do you have an estimated down time?

Reason- with the small cache that MW allows, I will be out of work in less than 30 minutes time.. So wondering if I should attach a backup project until the upgrade is completed.

Noticed you are going to be updated tonight, do you have an estimated down time?

Reason- with the small cache that MW allows, I will be out of work in less than 30 minutes time.. So wondering if I should attach a backup project until the upgrade is completed.

There shouldn't be any noticeable downtime.

---

Um, looking at the text in my results from OS-X running v0.12 stock optimized, there isn't the new tag thingie inside ... so, are we going to get a new version?

Or just get left to die on the vine?

---

Um, looking at the text in my results from OS-X running v0.12 stock optimized, there isn't the new tag thingie inside ... so, are we going to get a new version?

Or just get left to die on the vine?

really? it's there for me... what version of OSX are you using?

---

Um, looking at the text in my results from OS-X running v0.12 stock optimized, there isn't the new tag thingie inside ... so, are we going to get a new version?

Or just get left to die on the vine?

really? it's there for me... what version of OSX are you using?

10.5.6 Leopard ...

From the Sysinfo tool:

System Version: Mac OS X 10.5.6 (9G55)
Kernel Version: Darwin 9.6.0
Boot Volume: OS-X (Leopard)
Boot Mode: Normal


BOINC Manager 5.10.45 (RCN still does not recognize the new ID string for Macs when I try the 6.x series) ...

From Messages:

Tue Jan 20 21:58:23 2009||Starting BOINC client version 5.10.45 for i686-apple-darwin
Tue Jan 20 21:58:23 2009||log flags: task, file_xfer, sched_ops
Tue Jan 20 21:58:23 2009||Libraries: libcurl/7.18.0 OpenSSL/0.9.7l zlib/1.2.3 c-ares/1.5.1
Tue Jan 20 21:58:23 2009||Data directory: /Library/Application Support/BOINC Data
Tue Jan 20 21:58:23 2009||Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU X5482 @ 3.20GHz [x86 Family 6 Model 23 Stepping 6]
Tue Jan 20 21:58:23 2009||Processor features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1
Tue Jan 20 21:58:23 2009||OS: Darwin: 9.6.0
Tue Jan 20 21:58:23 2009||Memory: 16.00 GB physical, 202.74 GB virtual
Tue Jan 20 21:58:23 2009||Disk: 2.38 TB total, 202.49 GB free
Tue Jan 20 21:58:23 2009||Local time is UTC -8 hours
Tue Jan 20 21:58:23 2009|ABC@home|URL: http://abcathome.com/; Computer ID: 43311; location: (none); project prefs: default

I looked at the apps page and v 0.12 is the latest posted ... but the text in error out does not have your new ID stuff ...

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<stderr_txt>
called boinc_finish

</stderr_txt>
]]>

---

As I understand it the v13 is Windows only; Mac and Linux get v12.

App_name and app_version don't show in stderr out, those are in the result file that goes back to the server.

---

mic.

As I understand it the v13 is Windows only; Mac and Linux get v12.

App_name and app_version don't show in stderr out, those are in the result file that goes back to the server.

Hmm, then I must have mis-read the notes ... I could have sworn the notes said the keystring would be in the std/err out log ... well, if not, I guess I missed something ... if it is, then, the version I am using will stop giving me my cookies ...

{edit}
I have not done a task since the new test started on the server so no way to tell yet ... I have 3 queued up but not ready to run yet ...

---

As I understand it the v13 is Windows only; Mac and Linux get v12.

App_name and app_version don't show in stderr out, those are in the result file that goes back to the server.

Hmm, then I must have mis-read the notes ... I could have sworn the notes said the keystring would be in the std/err out log ... well, if not, I guess I missed something ... if it is, then, the version I am using will stop giving me my cookies ...

{edit}
I have not done a task since the new test started on the server so no way to tell yet ... I have 3 queued up but not ready to run yet ...

The app name/version is only in the result file sent back to the server. If you're using v12 for osx you should be fine.

---

The app name/version is only in the result file sent back to the server. If you're using v12 for osx you should be fine.

Then I misunderstood your notes ... not the first time and won't be the last (sadly, but humans are like that ... easily misunderstood) ...

---