From what I have seen on some boxes, BoincStudio reports a variable number of WUs.
When it delivers WUs, it reports a different number of WUs (probably the really installed number, would be 4 for a Dual Opteron Dual Core), whereas a work request seems to report a higher number.
boinc (Linux) / boinc.exe (Windows), it's the printf() format string for writing out the CPU information.
It is most likely identical in all versions (except for BOINCStudio maybe).
The modification still prints out the CPU information but preceeds it with a 1, a 4-CPU-machine has a 14 there, a 2 CPU machine a 12 and so on. You can verify that in my host list, all boxes with faster CPUs have 10 CPUs too many there.
The modification does not change the file size. If the file size changed, something went wrong and the file should not be used.
___________________
p.s.: if you're unfamiliar with this stuff and if you're using 5.3.12.tx36 (the current TruXoft client), you could give this one a try :
oct31.de/patched_trux_10.zip
BUT that one contains one more modification that resets the debit values to 0 on each BOINC restart. It's the one I am using - I hate it when a parked project inhibits caching for a running project :-/
only 128 WUs per day
)
The quota is 32 per CPU up to 4 CPUs, so 128 is the max no matter how many CPUs are in the system.
BOINC WIKI
BOINCing since 2002/12/8
From what I have seen on some
)
From what I have seen on some boxes, BoincStudio reports a variable number of WUs.
When it delivers WUs, it reports a different number of WUs (probably the really installed number, would be 4 for a Dual Opteron Dual Core), whereas a work request seems to report a higher number.
I am getting a message from
)
I am getting a message from the server saying I have reached the quota of 128.
I understand the 32/cpu/day limit but why a 4 cpu limit?
I have seen a Xeon III with 8
)
I have seen a Xeon III with 8 CPUs - I think it was at CPDN.
I guess those have really been installed CPUs as Xeon III had no HT and there was no BoincStudio back then either.
A dirty solution for the
)
A dirty solution for the calibrating Trux client is this btw. :
change this :
%d
into this :
1%d
Be careful to move the start tag one character to the left, i.e. :
3E 0A 20 20 20 3C 70 5F │ 6E 63 70 75 73 3E 31 25
replaces
3E 0A 20 20 20 20 3C 70 │ 5F 6E 63 70 75 73 3E 25
This would basically work with all clients of course
Ananas Which file are you
)
Ananas
Which file are you refering too?
boinc (Linux) / boinc.exe
)
boinc (Linux) / boinc.exe (Windows), it's the printf() format string for writing out the CPU information.
It is most likely identical in all versions (except for BOINCStudio maybe).
The modification still prints out the CPU information but preceeds it with a 1, a 4-CPU-machine has a 14 there, a 2 CPU machine a 12 and so on. You can verify that in my host list, all boxes with faster CPUs have 10 CPUs too many there.
The modification does not change the file size. If the file size changed, something went wrong and the file should not be used.
___________________
p.s.: if you're unfamiliar with this stuff and if you're using 5.3.12.tx36 (the current TruXoft client), you could give this one a try :
oct31.de/patched_trux_10.zip
BUT that one contains one more modification that resets the debit values to 0 on each BOINC restart. It's the one I am using - I hate it when a parked project inhibits caching for a running project :-/