Message boards : Server programs : CPID
Message board moderation
Author | Message |
---|---|
Send message Joined: 12 Mar 07 Posts: 59 |
Cross project stats on many (not all) of the stats sites depend on the CPID (Cross Project ID). Does the CPID still depend on having the same email address on all projects? I know it did at one time. Or is it enough to run both projects on the same computer (from the same client) at the same time ? If it is email dependent, how can a user keep the stats from a retired project where, by definition, it is no longer possible to update the email address? Edit - add: my understanding was that the older CPID would propagate anyway, but this seems not to be true if the emails are different. Can I force the one I want by judicious editing of the client state file? River~~ |
Send message Joined: 30 Oct 05 Posts: 1239 |
As far as I know (and take that with a grain of salt), it still only depends on email address. But I'm having a heck of a time getting my CPIDs to line up. They split last month and refuse to come back together. All the same email address and one project running on both computers. And I'm about to make it worse by changing to a different email adress for BOINC. I'm tired of Hotmail and it's crappy service. So I just created a gmail account only for BOINC. I do have one retired project, but since it only has like 50 credits on it, I'm not too worried about it. If I want it to show up in a stats box, I'll use Neil's site since it doesn't depend on CPID. Kathryn :o) |
Send message Joined: 27 Jun 06 Posts: 305 |
I think it is a technical requirement to stick the CPID to the EMail. Assume you have 2 accounts in project A, A.1 and A.2 Now run project B with only one account (B.1) on 2 hosts and add one of the two project A accounts to each of the hosts. Now B.1 syncs to A.1 on one host and B.1 syncs to A.2 on the other host This would either try to create two identical CPIDs (the CPID is unique!) on two accounts or it would never sync at all. ��u� |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.