How to combine stats for multiple machines

[bglynn]

How can i combine my work from multiple machines to my account?

 

[Napalm381]

Are you doing Dnet, Seti, or what?

 

[mechBgon]

In the projects I'm familiar with, simply use the same email address in the configuration of all the machines. This covers the RC5 and OGR clients, SETI@home, and I believe it applies to GammaFlux as well.

 

[bglynn]

RC5 - and that's what I did - same emais - but so far only the first system I setup is logging...

 

[bglynn]

Maybe it just takes time? This is the third day for the primary and second for my other 8 machines...and how long before I can be on TA? I went through the join motions yesterday afternoon...still not saying I'm on - bryan.e.glynn@bigfoot.com - shouldn't it say I'm on TA somewhere?

 

[TOOCOOL]

your on the team right here 1,895 and climbing😉

 

[bglynn]

Hey Mr. White-plains NY user of psi.net with an IP of 38.32.89.103 - you can't get my password so quit trying.

 

[mechBgon]

A couple questions:

The client is capable of doing OGR as well as RC5. I did not find you in the OGR-25 stats but it could be the case that your new cows are either 1) doing OGR instead of RC5 and their work has not shown up in the stats at Dnet quite yet, or 2) they are configured to do all the RC5 *and* OGR that they have, before they fetch and flush either one. It is easy to make them do what you want.

Double-click the cow icon in the System Tray to bring the client up into a window. If it is the latest version of the client, it may show the "Crunch-O-Scope", which is a real-time graph of the output. If so, click on View>Console so that it is in the text mode.

Now you can right-click in the window, choose "Configure," and then chose
2) Buffer and Buffer Update Options, and then
8) Load-work precedence ==> OGR,RC5,CSC,DES.

You can put "=0" after OGR if you don't want the client to do any OGR no matter what. That is the numeral zero, not a capital letter O, btw. However, if the RC5-64 key is found, the client will shut itself down, since it has been told not to do OGR.

As long as 9) Additional buffer-level checking ==> is not set to option 4, the client will not do all its RC5 and then all its OGR before fetching and flushing. I set my client up like this:

9) Additional buffer-level checking ==> 2
10) Buffer-level check interval ==> 0:30

so it will check every 30 minutes to see if there is any work to flush, and if so, it will fetch/flush. That works well for this system, which is on an always-on connection. I hope that is some usefulness to you. Another thing that would probably be really useful is to use the Team AnandTech proxy as your keyserver, because between the Weekstats pages and the Fullstats pages, you can see stats updates every fifteen minutes! 🙂 To use the Team Proxy, simply configure the client to

2) Automatically select a distributed.net keyserver? ==> no
3) Keyserver host name(s) ==> proxy.teamanandtech.com
4) Keyserver port ==>

 

[bglynn]

All my clients are configed to do only RC5. If I happen to find the key - how would I know it then?

 

[mechBgon]

You would know because the client would shut down immediately when a proxy or keyserver told it that the contest had ended. You would also get an email from Distributed.net to your cracking-email address if one of your computers finds the winning key.