News archive

Challenge results
First, wow and thanks everyone who participated! A special thanks to the Polish National Team for their work on the OpenCL app version for ATI cards.

The server held up nicely and as far as work hand out and return the only glitches that were raised relate to ATI cards having trouble receiving work and the massive bandwidth demands for the uploads.

Statistics are now final in the data for the team and user stats on the project home page. You will note that the timestamp on it is 10 mins after the end of the challenge but after comparing the team data from 16:05:03 to 16:10:03 there we no changes. There were some changes in points from 16:00:03 to 16:05:03 and this is because we counted all work by the reported time and not all the validation on the server side completed until the 16:05:03 update. These few changes are 10947.5 points for the Polish National Team, 3124.5 points for the SETI@klamm.de, 7823 points for Ars Technica, and 10947.5 points for TaiwainROC. Additionally, we have an archive of most of the statistics from the challenge available for public visibility, scrutiny, historical data, etc. via this archive.

From the start it looked like the Polish National Team was really putting some massive computation power to work and it began to look like Sicituradastra. was to be held at the number two rank. In the end Sicituradastra. did manage to finish in the top spot with a lead of approximately 353 (GPU) WUs in total where each team completed approximately 22000 WUs if just looking at credit of GPU WUs against the total.

On the user side [GPU Force] Robert 7NBI and STE\/E put out insane crunching efforts! They finished first and second.

The battles within various ranks of team and user are much more than just those at the top but equally interesting and best told by all those who wish to do so here. Congratulations to everyone!

The server saw some 40% increase in computational power from clients during the 3 day build up to the challenge and during the challenge. Initially it was only about a 12% increase towards the start.

Our biggest glitches related to getting boincstats.com data working correctly and some rather strange data for the last hour stats on our part. Then, of course no countdown clock, a wrong clock, etc.

Everyone wants to know if there will be another challenge and given how well this one seemed to go the answer is YES! No, we do not have a date or time yet. For now there is lots of work to do besides planning another challenge :) 10 Apr 2012 | 17:17:19 UTC · Comment

First ever project challenge
I am pleased to announce that we will be hosting our first project challenge!

Rainbow Resurrection: 2012-04-07 16:00:00 GMT - 2012-04-10 16:00:00 GMT

This 72 hour challenge will feature Primegrid style user and team statistics and only work handed out after the start time and returned before the completion time will be counted. In addition all WUs that are part of the challenge will receive 1.25x the credit that is received ordinarily.

The reason for this challenge is two fold:
1) The new hardware has been performing excellently and is averaging less than 20% utilization
2) An ATI/OpenCL app version is in early alpha stages and this challenge will be helpful in seeing if we can handle full 24/7 CPU+GPU where ATI will be added in the future. 31 Mar 2012 | 2:20:24 UTC · Comment

New server status 2012-03-17
We are fully moved to the new machine that was racked yesterday.

Update: the issues below are believed to be resolved for all new WU handout.

There are some known issues including:

1) some GPUs get no work (including my GPU)
2) some GPU WUs get incorrect credits for the work
3) some CPU WUs are monsters

The problem of very long tasks on the CPU I think are all GPU tasks going on to the cpu by mistake. Right now all the GPU tasks will be algorithm md5 (and later ntlm again) and the CPU tasks are mysqlsha1. That dynamic won't change for at least another 2 months. Also, the important thing in the tasks will be the chain length:
mysqlsha1_loweralpha#1-10_0_40000
md5_mixalpha-numeric#1-9_0_755000

https://www.freerainbowtables.com/en/tableprogress/

That's 40k chain length and 755k chain length. I think the longest chain length we've ever done on the CPU side is 60k. Our GPU work I believe has been 200k+ once we could no longer have the GPUs do the shorter CPU intended chain lengths without 100% crushing the server. 17 Mar 2012 | 20:22:17 UTC · Comment

2012-03-12 status
New WUs coming next weekend.

full details 12 Mar 2012 | 4:09:21 UTC · Comment

new status post and server 7.0.7
The server version has been updated and a longer status post maybe found in this post 13 Feb 2012 | 3:31:31 UTC · Comment

Validation errors?
To those of you whom are running the 7.x development client, you will get validation errors. To fix this problem, please downgrade your BOINC client to 6.12.34 which is the recommended version 9 Feb 2012 | 12:11:35 UTC · Comment

BOINC is up and running again
I'm happy to announce that we are finally up and running again at full speed!

To those of you whom might not now, we had issues with our brand new server. We were suffering from performance degradation and frequent spontaneous reboots.
Now we have migrated to a temporary loaner server while our original server is being tested to find the cause of the issues.
Previously it were running NetBSD 6.0 with LVM to manage the space, but we think it's what's causing the problems and so the server will be reinstalled with NetBSD 5.1 without LVM after the testing phase has completed, to keep things simple.

Until then, we hope you will help us test our temporary loaner server. Let's see how much it can take before going down
Let the crunching begin! 8 Feb 2012 | 8:19:33 UTC · Comment

Server issues hopefully isolated
Summary:
1) We are still alive.
2) No new work is being queued
3) We have two systems setup - both of which we can remotely power cycle
4) We're migrating to NetBSD 5.1-STABLE since we've ruled out hardware

Details:

My latest update. 29 Dec 2011 | 20:27:12 UTC · Comment

GPU work resume
Within about the next hour we will start WU handout for the next table.

more details 22 Dec 2011 | 4:44:29 UTC · Comment

WU handout stop (likely 2+ weeks)
More details in my post here. 30 Nov 2011 | 2:51:34 UTC · Comment

cuda work continues!
Martin and I determined what sets to do next and at the current rate this is 1.5 months of work. CPU work is already queued for 1week+ but we have a path on CPU work so we can keep feeding that queue.

The current cuda table is:
ntlm_loweralpha-numeric#1-10_0_344000x999424

This is a shorter chain length than the table winding down but the chain count has been increased to 999424. These WUs will be 7.625 MiB per upload and the chain count is aligned with cuda kernel call sizes. They should take longer than the current table per WU so the uploads should be less frequent. (Before changes these uploads would have been 9.53 MiB)

We still have the issue of perfecting keeping up so we will hit disk space issues in a little over a week with no perfecting at all. Of course we're perfecting as fast as we can so that should be considered a worst case scenario. 22 Nov 2011 | 18:16:52 UTC · Comment

cuda work status
In the next 2-4 hours the current queues of cuda work will be exhausted. Parameters for the next table are not yet fully concrete (we've been busy tending to server stability and scaling needs). It is unclear at this time whether this will be merely a few hours pause or perhaps a 2-3 day pause. Of course everyone, us included, would prefer the former.

If you'd like to set BOINC to prefer this project but defer to other projects if we do not have work then set the resource allocation in other projects to 0 and they will only become active when projects with > 0 allocations have no work available.

Also, the community never ceases to amaze! Trending data that we collect tends to become useless because the computation power, especially the cuda power, grows faster than expected.

We will try to continue to keep everyone updated and in any case this should not be anything like a week+ shutdown as we've had in the past. 22 Nov 2011 | 6:51:32 UTC · Comment

crunch on!
more detailed status 15 Nov 2011 | 5:59:36 UTC · Comment

testing changes (small work handout)
Martin is testing some changes to the assimilator and the work hand out is only a small batch and is not yet a full restart. 12 Nov 2011 | 19:59:17 UTC · Comment

2011-11-02 update
It may easily be a week before we can hand out WUs again.

details of status 2 Nov 2011 | 0:55:22 UTC · Comment

2011-10-31 07:13 UTC quick update
CPU only work is being handed out right now. (It's 02:13 here and I have work in the morning so I'll save the more detailed post for later).

We essentially resolved major issues like data corruption on uploads, down to up to 4k WUs marked invalid and possibly will be marked valid when a valid result is return, and have a large backlog of assimilation and perfecting.

We focused a lot of efforts on the scheduler, feeder, work generator, validator, etc. which are the pieces that directly impact crunchers *but* increasing multi-TB build up from those optimizations means that the assimilator and the perfecting runs have room for improvement and a backlog of some ~200k WUs.

We have work already ready to be queued with the flip of a flag but have around 6TB of data to get processed before we can release more work. We delayed in any status updates as we hoped to have some sort of time line but it seems better now to at least keep communication flowing even if we cannot give any exact time line.

We aren't going away but just have large backlogs. The majority of the data on the table progress page refers to tables that have completed generation but need assimilation, perfecting, and conversion.

I'll try to provide a better update with more details within the next 24 hours. 31 Oct 2011 | 7:22:44 UTC · Comment

stability restored
Summary: bad network card

details 28 Oct 2011 | 3:39:33 UTC · Comment

credits!
Our first validator snafu was more minor in scope and something that did not seem to justify the time commitment to work on correcting the credits.

However, the issues over the last 24-48 hours have been so severe in scope and impact that there was nothing fair about just say tough. Also, based on data that continues to remain favorable it seems that somewhere between: heat, load, or power supply lays the culprit. We continue to run in as trimmed down a fashion as possible to allow WU hand out, validation, and credit. This will continue until our host gets some high cfm fans in place or we need to stop work hand out due to disk space.

I spent this evening writing code to grant credit to results that failed validation but match the result marked as valid for the workunit. The updates have been applied for the result, host, user, and team total_credit. I did not try to adjust all the expavg values *just* total_credit. Also, please note that applies to WUs that already have a valid result turned in *and* up to and including the past 10 days.

There are many results waiting for a result to mark the workunit valid and will allow me to run this code again. Please note this code is very specific to the two issues encountered between the validator failures and the upload handler failures that resulted in validation failures. Also, please note this level of credit adjustment marks the most extreme needed and applied in the history of the project under BOINC in over 3 years.

We certainly cannot promise that every single cobblestone has been granted or will be but I think everyone should be fairly accepting of their credits versus a few days ago. Please use the forums to discuss this and other issues as much as possible. Our admin staff of 2 people, who both have full time day jobs, is not able to investigate every single user. Hopefully though this adjustment and ones to come as soon as a valid result+workunit are available to DC against will overall be fair in compensating everyone. 26 Oct 2011 | 6:09:17 UTC · Comment

status update on server errors
We have essentially the web site, scheduler, and validator running. The assimilator, perfecting, etc. are not running. The error rate has been 0 since we dropped the other daemons, watched the load dropped, and restarted the machine. However, this is not to say that the problem(s) are resolved as we are testing to see if our current theories have correct.

Martin, our host, and I have been exploring particularly thermal and power issues. (Martin found the upload handler was writing 16KiB chunks to disk but optimization to that helped load but didn't change uploaded files getting corrupted.) Also, the upload handler is essentially the least changed, untouched, and until now basically the upstream boinc code. At present the load is staying low and so are the CPU thermals.

Our I/O upgrade only changed the RAID controller and the drives but 3 of the drives were running hotter than they should have been. This extra heat of course impacts the heat in the system.

We have the disk space to keep running in a minimal mode like we are now. Our host already has a heavier power supply and high cfm fans ready. We also are planning some contingencies if we still have problems at that point. 25 Oct 2011 | 21:10:07 UTC · Comment

CPU work queue empty
The CPU work queue is currently empty. This means that all of the hybrid2 WUs are in progress to finish that first hybrid2 set.

A bit of poor planning on our part as we could watch all week as the CPU queue was draining and we don't have the next batch queued.

I have code changes essentially ready for retooling the work generator, scheduler, and validator but Martin and I haven't had a chance to touch base yet. I expect we should get everything ready to go and rolling again within the next 24 hours.

*note* plenty of cuda work remains. We attempted to cross the steams, in that we assigned some CPU work to the cuda side and it didn't go well for clients. Kicking cuda work over to CPUs would result in WUs that are a good 7 times longer. Some may not mind if they have crunched any of the really long tasks on Primegrid but it seems like a bad idea over all :) 23 Oct 2011 | 2:01:46 UTC · Comment

report_deadline extension for credits
Thank you for the PM xyzzy as I got lost in all of the insanity. Ensuring people aren't penalized for WUs because of the upgrade outages is something I had already promised.

For all WU's with a report_deadline between 2011-10-09 00:00:00 - 2011-10-13 00:00:00 GMT I have added 48 hours to the report_deadline. Actually this would have decreased server load earlier.

What happens when the deadline passes is a 2nd WU is generated and sent out. Whichever WU is reported first is granted credit and the server sends an abort at the next network communication to the other client. This is the default BOINC system and in some cases may unfairly punish the 2nd cruncher.

feedback requested: If you have fallen victim to the server outages and think the adjustment needs to be different from the above then please post here or PM me. We absolutely do not want to have earned credit lost because of issues on our side. 11 Oct 2011 | 23:55:35 UTC · Comment

I/O upgrade completed
Everything should be operating normally. We're finished with the hardware swap and then the core pieces for data syncing. 10 Oct 2011 | 21:20:08 UTC · Comment

I/O upgrade start time from host 2011-10-10 05:00 GMT
max 4 hours of downtime 10 Oct 2011 | 2:31:10 UTC · Comment

I/O upgrade, no really
2011-10-10 start between ~02:00 - 06:00 GMT with a planned max down time of 4 hours. 9 Oct 2011 | 6:33:38 UTC · Comment

another GPU work stoppage
Summary: watch the backlog queue on the graphs page.

more details 5 Oct 2011 | 18:32:35 UTC · Comment

upgrade not quite yet
*groan*

"I went down there and started getting ready... Looking inside, the RAID card will need one 8087 to SATA right angle and one 8087 which extends straight."

Card came with 2 straight cables. 3 Oct 2011 | 15:10:15 UTC · Comment

cuda work stoppage
We currently are not handing out cuda work. First, due to the server backlog and second because our host says this Sunday night (GMT -7) the I/O upgrade will finally happen! 30 Sep 2011 | 20:17:15 UTC · Comment

cuda work/project status
New hardware install is coming next weekend. more details 11 Sep 2011 | 1:06:52 UTC · Comment

new cuda work
Just released cuda work. Instead of releasing a whole table at once this is 1/4th of a table. Hopefully this means more frequent batches of work released and less extremes of getting behind. We have again made several changes that should help the server cope better than before but we have a stop gap to let us confirm that. Also, things are moving forward with our new I/O layer. Expect a full project status announcement in the phpBB forums within the next few hours. 4 Sep 2011 | 23:19:01 UTC · Comment

server needs time to catch up
Validation is getting further behind, on purpose, because we need assimilation to catch up and clear some of the space for incoming work. We're going to let the current batch of work run out and then let the server catch up.

I also have this to share from our host:
"I think that if we put the drives and card in another machine and stress test the heck out of them starting this weekend (3rd & 4th of September), we can leave that machine running all week and I can install everything on the following weekend (the 10th and 11th). " 30 Aug 2011 | 20:47:30 UTC · Comment

some hiccups on the restart
The restriction on processes for the boinc and apache users was set far too slow and prevented especially schedulers from spawning. If you have had issues reporting work or receiving work then this should now be resolved.

Other than that our bandwidth incoming is returning to pre-stop levels. The validator is keeping up thus far and the assimilator is continuing to make progress even in the face of perfecting and conversion runs. 28 Aug 2011 | 16:29:20 UTC · Comment

WU generation resumed
For a bit of timeline see: https://www.freerainbowtables.com/phpBB3/post18240.html#p18240 27 Aug 2011 | 23:09:19 UTC · Comment

Work generation has been stopped
We have temporarily disabled work generation due to our server being overloaded, but there is still around 5000 WU's left.
As soon as we are able to keep up with the work received, we will enable the work generator again.
We had to take this measure to make our server responsive again.

Thanks to everyone for their massive support to our project! We will make sure to keep you updated as soon as the work generator is running again 24 Aug 2011 | 19:34:18 UTC · Comment

windows cuda 3.44 release
3.44 is out with higher priority for the CPU side of the GPU tasks and the scheduler was updated to use 0.01 CPUs. Both are to try to sort out some of the low GPU utilization or stuck/hung/idle GPUs. If these don't do the trick then there is at least one other change we will try reversing.

All feedback is helpful! Whether good or bad esp on: desktop latency, cpu usage, gpu utilization, etc. 19 Aug 2011 | 23:53:25 UTC · Comment

slow validation
Yesterday and today we have had some periods where the server has been a bit backlogged. Please be patient as the backlog will clear eventually.

Yesterday we learned about which disk spindles to *not* use for output of perfecting runs with the I/O what it is these days.

Today among other things I learned that our twice a day database backups are too much for the I/O and have changed it to only daily.

Please note that in all cases that have been observed the system is not in any way CPU or RAM limited and it is just the I/O layer mentioned on the website and in the forums that needs a major overhaul. On this front we have everything speced out but am waiting to hear from our host on ensuring there is sufficient power into the rack. 19 Aug 2011 | 0:33:47 UTC · Comment

New speed record (15 bil links/sec)
DistrRTgen generation speed has increased by 50% in little less than a day! We are now doing 15 bil links/sec. See https://www.freerainbowtables.com/phpBB3/topic2952.html for a new graph on the project website! 12 Aug 2011 | 15:38:29 UTC · Comment

CUDA 3.2 update
Apparently there was some issues with the CUDA 3.2 app released yesterday.
It has now been updated to 3.39 to solve those problems 12 Aug 2011 | 5:27:42 UTC · Comment

New Windows CUDA 3.2 app release
We have released a CUDA 3.2 version of Windows distrrtgen. DistrRTgen will no longer suck 100% of a single processor anymore, so you can use it for other calculations! 11 Aug 2011 | 20:03:02 UTC · Comment

project milestone of 10 bil links/sec
A new project milestone of 10 bil links/sec has been hit and new eye candy has been added to the site. See http://bit.ly/p2MR7s for more details! 11 Aug 2011 | 17:26:52 UTC · Comment

2011-08-03 project status update
http://www.freerainbowtables.com/phpBB3/topic2920.html 4 Aug 2011 | 1:43:36 UTC · Comment

x86_64 windows build fixed
It's 3.30 and is returning valid work units. 1 Aug 2011 | 15:37:06 UTC · Comment

distrrtgen updates and improvements
Martin and I bumped everything to 3.29 to match version numbers but the x86_64 windows build has 100% failure rates and is not yet resolved. Also, the updated versions all have the hybrid2 updates for the cpu side.

3.30 for x86_64 linux cuda is now out and drops the cpu usage to a tiny fraction of what it was. On my system the cpu usage is <= 1% instead of nearly a full CPU. I do get about a 3-4% decrease in generation performance but think this is an acceptable trade off.

Please report any bugs or feedback (especially on the change in the cuda performance on x86_64 linux.) If this trade off remains acceptable then it will come over to the windows build as well. 31 Jul 2011 | 1:55:31 UTC · Comment

cpu distrrtgen_3.25_i686-pc-linux-gnu
While the x86_64 update shows a 100% pass rate over the last 24 hours, the 32-bit version shows a high failure rate. All of the errors are executing the binary. If you are running into this problem then find your project path (ex: /var/lib/boinc-client/projects/boinc.freerainbowtables.com_distrrtgen) and issue a sudo chmod a+rx distrrtgen_3.25_i686-pc-linux-gnu.

I have no idea why this is an issue as it never has been before and it should impact x86_64 equally. Additionally, it doesn't seem BOINC version specific since everything from old versions to the latest version are hitting this problem. 30 May 2011 | 19:49:01 UTC · Comment

planned server maintenance
This did not take place yesterday but should this time.

Planned start 2011-05-20 05:00-06:00 GMT and expected duration of about 1 hour. 19 May 2011 | 0:00:46 UTC · Comment

project status update 2011-05-17
Project status update see http://www.freerainbowtables.com/phpBB3/topic2813.html 18 May 2011 | 2:09:28 UTC · Comment

Server backlog update!
Our backlog on the server is now so severe we had to disable the work generator to keep up with the backlog. Our server drives were running full from results uploaded by our users. We expect to reenable the work generator within 48 hours.
To prevent this in the future, we are investigating different options of upgrading our server to be able to handle the increasing load.
Note: Do NOT cancel your existing work units. The server still recieves results from the clients 13 Mar 2011 | 21:15:54 UTC · Comment

status update 2011-03-03
Backlog on the server side for the assimilator full details on status and changes are in the primary forums. 4 Mar 2011 | 3:06:00 UTC · Comment

back to normal status
crunch on! 1 Mar 2011 | 5:45:20 UTC · Comment

more growing pains
NTLM (md4) over the MD5 WUs are really hitting the server especially with the GPU WUs. As such a couple conditions occurred that the safest approach was to take down the boinc daemons while the jobs to clean everything up run. One condition has been fixed outright so that it can never happen again and the second condition has had monitoring added. All the daemons should be running normally again within the next couple of hours. 1 Mar 2011 | 5:04:12 UTC · Comment

next set, hybrid2, and general status
We are currently wrapping up generation of the set md5_mixalpha-numeric-space#1-8.

PowerBlade and I have been frantically getting hybrid2 support completed, tested, and deployed in preparation for our next set. This will be a hybrid ntlm set as mentioned in my last post: hybrid2(alpha#1-1,loweralpha#5-5,loweralpha-numeric#2-2,numeric#1-3). We finished pushing out client binaries and server binaries not long ago. There is a small test set with 100 WUs running through the system now before we kick this one off. Also, the code was crudely hacked on over last weekend and will perform slower than it should, which will be the next item on the todo list after we kick this one off. Finally, I still have to complete the changes to the cuda code changes for hybrid2 support.

Once the new set is running with cuda and with optimizations to follow within a week or two, then I'll return to rti2 so the set we just finished can be converted to rti2 for distribution.

Also, we've had several project members come forward with the starting work for a cross platform GUI for rcracki_mt. I'm pleased to say that Paragon's work is near a place where it will be merged into the head branch. 1 Feb 2011 | 2:44:36 UTC · Comment

table set completion and next table set
All available WUs have been assigned. Our next set is going to be: ntlm [A-Z][a-z]{5}[a-z0-9]{2}[0-9]{1,3}

Details of the set may be found in the discussion in the forums.

I'm in the process of fixing hybrid support and rolling out new server side and client components in order to start this set. Hopefully this will be complete within the next 24-48hours. 30 Jan 2011 | 16:47:16 UTC · Comment

server stability
Some of you may have noticed that the webserver for boinc has been a bit flaky yesterday and today. This is not failing hardware or DoS attacks or anything of that nature. We're just getting more growth both in users and in work generation and I'm still tweaking some settings to handle it. 18 Jan 2011 | 19:46:29 UTC · Comment

FreeBSD native distrrtgen
I started to get more requests for a FreeBSD native distrrtgen than I do for OSX and have created one. (OSX is a much larger pain.) For those on FreeBSD:
cd /usr/ports/net/boinc-client && make install and then assuming you already have an account and don't want to use the GUI:
/usr/local/bin/boinc_cmd --project_attach http://boinc.freerainbowtables.com/distrrtgen/ <key>

I keep getting some NetBSD requests as well. Please feel free to email/pm/comment on machines processor and hardware support that you are waiting for.

UPDATE apparently FreeBSD breaks binary ABI compat with every release (4.x, 5.x, 6.x, 7.x, 8.x) so this build only works on 8.x. I'll go dig up my archives and make a "compatible" 4.x build or something of that nature. 8.x supports all the way down to 4.x but 7.x doesn't even support 8.x.

UPDATE 2 x86 FreeBSD 7.x and 8.x distrrtgen binaries are now available. I already have received requests for 6.x and x86_64. Does anyone by some awful reason have systems that have spare cpus and are FreeBSD < 6.x?

UPDATE 3 x86_64 FreeBSD 8.x distrrtgen binaries are now available as well 10 Jan 2011 | 6:19:16 UTC · Comment

md5_mixalpha-numeric-space#1-8
This set should complement our md5 tables nicely as we have ntlm_mixalpha-numeric#1-8 already. This one is a larger keyspace and we've moved from 40k to 60k length chains in preparation for sse2 code completion for distrrtgen as well as sse2 and cuda making it to the rcracki_mt side. Additionally, this table set should take some time to generate such that code can be completed for the projects mentioned, rti2, and more. See the forums linked in the last news post if you want to see and discuss plans for the set after this one. 1 Jan 2011 | 1:29:54 UTC · Comment

next table to generate
In the next 24-48 hours all WUs for the current tables listed on the table progress page will be handed out to clients. Please help decide the next table set to generate by participating in the forum discussion. 31 Dec 2010 | 4:41:05 UTC · Comment

Momentary hiccup a few hours ago for uploads
The issue has been corrected and is a result of increasing user base. 29 Dec 2010 | 22:05:21 UTC · Comment

BOINC stats working again
BOINC stats is finally up and running again, so we export our XML data now. On top of that, a 2.28 version has been released for Linux x86 and x64 for improved speed! 25 Oct 2010 | 0:00:00 UTC · Comment

Distributed rainbow table checker is now online!
The apps Index Calculator and Chain Checker is now released. Together they form the distributed rainbow table checker service on our site. If you don't wish to run those apps, go to your account settings at http://boinc.freerainbowtables.com/distrrtgen/prefs.php?subset=project and turn them off 29 Nov 2008 | 0:00:00 UTC · Comment

Linux clients has been updated to 2.24
This update removes the depency for libssl 28 Nov 2008 | 0:00:00 UTC · Comment

Credits for WU's has been increased
The credits for each WU has been increased to 50 for the current WU's. This is done to make it easier to compare the stats with other BOINC projects 26 Nov 2008 | 0:00:00 UTC · Comment

DistrRTgen goes out of beta
DistrRTgen is finally out of beta and is now in production mode! Let the race to the top begin! 26 Nov 2008 | 0:00:00 UTC · Comment

News is available as an RSS feed RSS