utopia-i wrote:PinkPenguin wrote:TJ's stats and BOINCSTATS now only have two utopia-i's each. Only four projects to bring into line: NumberFields, Seti, SIMAP and SubsetSum... should be OK by the weekend. 8)
2 weekend later still have a twin ..
http://homepages.ed.ac.uk/kennys/current.png
ideas ?
Hopefully your client is later than v6... if not > update it... (sorry, had to make sure!)...
The short answer is: "Attach the project with the oldest join date to your client for a while" (1 or 2 weeks maybe).
In your case this would be one of CPDN, WCG, ABC, ALBERT, EINSTEIN, YOYO, MILKYWAY in that order - I would attach CPDN with "no new tasks" as they are really long runs these days if you can get them... EINSTEIN or MILKYWAY are probably a good choice to run as they are older than the four non-aligned projects and you have better visibility of CPIDs and things through your account than WCG. I think YOYO has an older server so it may not be the best one to actually run for a while.)
As you always use the same eMail and PWD on all projects there is very little else you can do. Please note, given the detail that follows, that the higher CPID is what is on your non-aligned projects so you want these to align with the older, lower CPID.
I think you would need Numbers, SIMAP, Seti and Subset to align with big group - the other way round would be a problem as some projects simply wouldn't come into line the other way round. If you are a little paranoid like me I would probably stop running numbers for a while and run one or two of the older projects for a few days before restarting numbers.
Here's the full detail from the FAQ on Mundayweb if you are interested (
http://boincfaq.mundayweb.com/index.php?view=192):
The Cross-Project Identifier is a 32 character hexadecimal key that combines the MD5 hash of your domain name, IP address, free disk space, and a timestamp of your computer on a project, locked to your email address (the unique identifier).
The CPID is used by statistics sites to quickly see which projects your computer is attached to.
The projects do not communicate your CPID directly between projects. The CPID has to go through your computers in order to synchronize. So, if you have multiple computers attached to multiple projects, there must be a path from project server to client to project server that covers all projects to which you have computers attached. There must also be successful communications between the client and the project server to update the project server with the CPID.
The CPID changes if you change the email address, and the email address used at each project must be the same as that used for all other projects you are attached to.
Older clients will switch to the higher CPID when a project generates a new CPID. Newer clients will keep the CPID from the project with the oldest join date. Note that because this date is not transferred back to the server except with version 6 clients and the most recent servers, there is a bug where the CPID can be split and one project flips between these two. If this is the case, attach the project with the oldest join date to all hosts for a while.
Oh, and by the way, best of luck...