OGR is BACK!

[DJ_D]

OK, I don't understand why my client switched over. I am using client V2.8007-458, and I had this in my INI file.

[misc]
project-priority=DES,CSC,RC5,OGR

The way I understand it, my client should not have started doing OGR until RC5 was done, but this morning my client had switched over and was doing invalid work! I will have to hurry home and fix my home machines.

I added OGR=0 and everything is cool now, but I bet a majority of clients are going to switch over and do nothing. Shazbot! :Q

PS D.Net is not about proving the quality of 64 bit encrytpion (IMHO). D.Net is about making a huge distributed network of computers to tackle awesome problems. So it only makes sense that the people at D.Net are looking for more useful projects, but I pretty much do it for the stats. We are close to passing /. and taking the number 1 spot. I want to stick with that goal for now.

PPS vss1980 - Internet Explorer uses public key encryption, which is not nearly as strong as private key encryption like RC5. Web browsers can't use private key because there is no secure way to transmit the key. IE has to use twice the bits of RC5-64 to get anywhere near the same level of security.

 

[Viztech]

DJ-

The reason your clients behaved that way is that you set RC5 as the 1st priority. In other words, when the client ran out of RC5 blocks, it switched to OGR. When you would run out of OGR blocks, it will flush and switch back to RC5.

By adding the =0 to the project, it shuts that project down.

viz

 

[TheyCallMeSAK]

Too bad there isn't good client management software for cow's. This could help with mad cow disease problems. I suppose it would require DLL though. Thus removing the security of the clients, right?

 

[SSP]

damn.. the client's doing OGR projcts... must stop it now!!!!

F`uck! No wonder I had 500blocks completed yesterday. Where do I check my OGR stats then?

 

[DanC]

I'd sooner visit the dentist.
That sucks to have to change all the clients.
I'm considering pulling everything out altogether.

 

[Ken g6]

SAK: If you're on an NT network, you might try Remote Cows: http://www.distributed.net/download/addon.html I've never tried it, but I hear it works great.

 

[ViRGE]

Pproxies can also help here, since you can make them tell the clients that OGR is closed, even when it isn't.

 

[Batti]

DanC, all you need to do is propogate an edited ini via a script. Or if you're using Remote Cows, you can redistribute the client via that. No need to visit the machines at all.

 

[DJ_D]

Viztech, OK I think you're right. I forgot how my clients at work are configured. They are set to do about six hours of work and then flush, so they run out of RC5 blocks every six hours. When they ran out of RC5 they switched to OGR, which makes sense.

I used to have them download several hundred blocks and update to a Pproxy after completeing 1 block, that method would never have run out.