Quick question guys about this INI file

[Adul]

I trying to set it to do ogr when rc5 runs out. Does this look right?


[parameters]
id=tncrc5@home.com

[networking]
keyserver=http://teamanandtech.dhs.org
encoding=
disabled=no
nettimeout=14
nofallback=true
autofindkeyserver=no

[misc]
run-work-limit=0
project-priority=RC5,OGR

[rc5]
randomprefix=207
fetch-workunit-threshold=30

[buffers]
allow-update-from-altbuffer=yes
frequent-threshold-checks=4

[triggers]
restart-on-config-file-change=yes

 

[nickdakick]

<< id=tncrc5@home.com >>


This line is defintely wrong, it should look like this: id=rc5@tacube.com
No, just kidding.

 

[Adul]

sure nick. anyways, does it look right or not?

 

[Joe O]

Yes!

 

[Kilowatt]

It looks OK for doing OGR instead of RC5.

[misc]
run-work-limit=0
project-priority=RC5,OGR=0

Will do RC5 only

[misc]
run-work-limit=0
project-priority=RC5=0,OGR

Will do OGR only

The way you have it, it'll do OGR untill no stubs are left, then switch to Rc5 untill the next update.

 

[Engine]

Actually, it's the other way around, isn't it? Since the project priority has RC5 first, it'll do RC5 as long as possible, and if it runs out of blocks and can't get any more it'll switch to OGR.

 

[BurntKooshie]

I believe, though I am not certain, that having a config of RC5, OGR=0 means that it will exclusively do RC5. Even if it runs out. The only way it would switch to OGR is if the contest were to end. I <think> this is right. Someone could easily prove me wrong.

 

[JHutch]

Adul,

Your ini is right.

OK, guys, quick refresher...

The &quot;preferred&quot; way to do RC5 only is to have:

project-priority=RC5,OGR

-and-

frequent-threshold-checks=4

This will start RC5 blocks and run them until the rc5 buffer runs out. Then, it will fetch and flush. It'll keep running RC5. The only way it switches to OGR is if the RC5 buffer runs out and it is unable to get more blocks. This is a good thing, because it keeps the client from cracking randoms. Plus, when the RC5 contest is over, your client will automatically switch to OGR without you having to do anything.

This method has gone into the &quot;official&quot; team FAQ and I think Russ was going to change his &quot;floppy&quot; install to use this method.

JHutch

*edit* To do OGR only, just reverse the project line to OGR,RC5. It will keep cracking OGR unless it cannot get anymore OGR stubs...

 

[Engine]

I'm pretty sure that the OGR=0 means that the client won't switch to OGR even if RC5 were to end. If RC5 ended the client would probably just shut itself down or work on randoms indefinitely.

I posted a thread about this a little while back, titled &quot;OGR=0?&quot; raising a concern I had about this issue. I'm pretty sure that this will cause the client to work on the highest priority project for as long as possible (IE until it can't get any more work for that project or the project closes).

[misc]
project-priority=RC5,OGR

[buffers]
frequent-threshold-checks=4

Edit: Heh... Hutch is faster than I am, so just ignore this post

 

[nukefarmer]

if you want the client to alternate between ogr,rc5 and back, i'm using following ini settings:

[misc]
project-priority=OGR,RC5

[rc5]
fetch-workunit-threshold=32
preferred-blocksize=32

[ogr]
fetch-workunit-threshold=2

[buffers]
frequent-threshold-checks=0

This will first do 2 ogr stubs then 32 rc5 blocks and then switch back to ogr after fetch/flush. Adjust workunit tresholds to your needs.

 

[Adul]

oh that sounds cool to me

 

[Adul]

Ok i got some setp.exe files made for the TNC crowd