It looks like everything is coming back just fine with the new application versions, so I've started up a batch of fresh runs which will mean a lot of new workunits. Happy crunching!

What's the difference with old app??

same question here... The new one is built linking glibc 2.14 and that prevents WU from running on debian wheezy, while release 0.50 was running fine.

TIA
Andrea

Travis,

Gibbs_0.51_x86_64-pc-linux-gnu

0.51 is requiring newer GCC and G++ libraries than 0.50 required, and as such many older machines are now incompatible. This is same problem that occurred with the last update to subset last year.

Travis,

Gibbs_0.51_x86_64-pc-linux-gnu

0.51 is requiring newer GCC and G++ libraries than 0.50 required, and as such many older machines are now incompatible. This is same problem that occurred with the last update to subset last year.

Any chance you could let me know what would be a good version of the GCC and G++ libraries to link? I can try and get an older compiler installed to link against.

Not so easy to give a good guess; Debian, which is quite conservative on package upgrades, provides these:
- current stable release (jessie, released in april 2015): gcc-4.9, glibc 2.19
- old stable release (wheezy, released in may 2013): gcc-4.7, glibc 2.13
- old old stable release (squeeze, released in february 2011): gcc-4.4, glibc 2.11
while these should be the packages in Ubuntu:
- wily werewolf, released in october 2015: gcc-5.2, glibc 2.21
- trusty tahr, released in april 2014: gcc-4.8, glibc 2.19
- precise pangolin, release in april 2012:gcc-4.6, glibc 2.15
I took a look also at an old fedora 12 released in 2010: gcc-4.4, glibc 2.11
and a Centos 6.5 released in july 2011: gcc-4.4, glibc 2.12
(release versions taken from distribution repositories, any mistake is mine)

That said, it's all up to you :)

my 2c is that rel. 0.50 was working fine, or at least nobody complained on this forum, so the same settings would be fine.

Hi Travis,

there seems to be a buffer limit in place of 4 workunits per core. Would it be possible to raise that number to (at least) 10 or so? Most of the workunits take just 30 seconds to about 5 minutes to process, which means I'm running out of work frequently at the moment. Thanks!

I noticed the same thing. Some tasks take also 10-20 seconds to terminate and I receive 10-15 points. It would be nice to have longer tasks or more ones per core

I noticed the same thing. Some tasks take also 10-20 seconds to terminate and I receive 10-15 points. It would be nice to have longer tasks or more ones per core