Client keeps switching between OGR & RC5

[Choralone]

I recently started running OGR on two of my fastest machines at home. Mainly because I want to help TA regain the #1 position before it's over. On my main machine (A Celery 2 566->850) the client will do two OGR packets (what I buffer since I'm on @home) and then crunches RC5 for about 3 hours (what I have it set to buffer at a time). My question is has anybody else seen this? The reason why I ask is that my other machine (a P3 600mhz) is also setup the same way using the same client but does not do that. I even compared the .ini files on each machine and they're nearly identical. Only difference being the P3 is a laptop and has a couple extra lines telling the client not to pause when on battery power.

 

[Viztech]

Hmmm
Do you have this in your ini?

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

It sounds like you are rolling between projects, which is what will happen in a default Dnet client configuration.
There are several ways to stop it, but this is one of them.
If you are on 24/7, you could do this as an alternative.

[buffers]
alternate-buffer-directory=
checkpoint-filename=cp
frequent-threshold-checks=3

The last line will update with the keyserver/proxy as each OGR unit is completed. This way the OGR buffers stay full and it will notm roll ahead to RC5. Essentially this is what I do on all my OGR machines. If the contest becomes closed or can't connect to the proxy, it will automatically switch to RC5.

Welcome to OGR!

viz

 

[Choralone]

Thanks viztech! That must be what's happening. I thought though that if you have OGR specified before RC5 like in the line you posted that it'll work on OGR unless those packets are not available when it tries to fetch more. Like if OGR is closed. But I'll try adding those other lines when I get home from work.