File: README

package info (click to toggle)
cpushare 0.48-4
  • links: PTS, VCS
  • area: main
  • in suites: squeeze, wheezy
  • size: 380 kB
  • ctags: 308
  • sloc: python: 1,102; ansic: 749; sh: 265; makefile: 205; asm: 27
file content (128 lines) | stat: -rw-r--r-- 6,258 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.  See the GNU LESSER GENERAL PUBLIC LICENSE for more details.

THE USE OF ALL THE SERVICES PROVIDED AT THE CPUSHARE.COM DOMAIN, THE USE OF THE
CPUSHARE SOFTWARE, THE USE OF THE CPUSHARE LIVE CD, ARE ALL AT YOUR OWN RISK.

ANDREA ARCANGELI, CPUSHARE.COM, ITS SUPPLIERS, AND THE OTHER PARTIES INVOLVED IN
CREATING AND DELIVERING ALL THE CPUSHARE SERVICES AT THE CPUSHARE.COM DOMAIN,
THE CPUSHARE SOFTWARE AND THE CPUSHARE LIVE CD, SHALL NOT BE LIABLE FOR ANY
SPECIAL, DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, CONSEQUENTIAL DAMAGES OR OTHER
LIABILITY OR OTHER DAMAGES WHATSOEVER INCLUDING WITHOUT LIMITATION: LOST
REVENUES, LOST PROFITS, DATA LOSS, HARDWARE DAMAGE, EXPOSURE OF CONFIDENTIAL
DATA THROUGH THE INTERNET, SPREAD OF VIRUSES OR TROJANS OR WORMS OR ANY OTHER
MALICIOUS SOFTWARE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE CPUSHARE
SERVICES AT THE CPUSHARE.COM DOMAIN OR THE CPUSHARE SOFTWARE OR THE CPUSHARE
LIVE CD OR THE USE OF OTHER CPUSHARE RELATED DEALINGS (HOWEVER ARISING,
INCLUDING NEGLIGENCE).

YOU MUST UNDERSTAND AND ACCEPT THAT RUNNING THE CPUSHARE SOFTWARE WILL
INCREASE YOUR ELECTRIC BILL, THAT IT WILL INCREASE THE UTILIZATION OF
YOUR NETWORK INDEFINITELY, THAT IT WILL POTENTIALLY AGE ALL YOUR
HARDWARE COMPONENTS MORE QUICKLY, THAT IT WILL SLOW DOWN YOUR COMPUTER
AND THAT IT WILL REDUCE THE AVAILABLE RAM. IN ORDER TO USE CPUSHARE
YOU MUST AGREE TO PAY FOR ALL ELECTRICITY COSTS, FOR ALL NETWORKING
COSTS AND FOR ALL HARDWARE PART REPLACEMENTS. THIS IS TRUE EVEN IF
YOU'RE NOT ACTIVELY EXECUTING A TRANSACTION. FOR EXAMPLE THE CPUSHARE
GLOBAL BENCHMARK WILL RUN ON THE SELLER COMPUTERS AT REGULAR INTERVALS
OF TIME, AND IT WILL GENERATE CPU, RAM AND NETWORK LOAD EVEN IF THE
SELL ORDER ISN'T EXECUTING A TRANSACTION YET.

THE REDISTRIBUTION TO THIRD PARTIES OF ANY CPUSHARE SELL ORDER OR OF ANY
CPUSHARE LIVE CD (WITH THE SELL ORDER HARDCODED INSIDE) THAT YOU DOWNLOADED FROM
THE CPUSHARE.COM WEBSITE IS AT YOUR OWN RISK.

YOU'RE STRONGLY RECOMMENDED TO WAIT ANY THIRD PARTY TO REGISTER HIS OWN CPUSHARE
ACCOUNT BEFORE REDISTRIBUTING ANY CPUSHARE SELL ORDER OR ANY CPUSHARE LIVE CD TO
SUCH THIRD PARTY. YOU ARE RECOMMENDED TO SHARE YOUR SELL ORDERS OR THE CPUSHARE
LIVE CD (WITH THE SELL ORDER HARDCODED INSIDE) ONLY WITH PEOPLE THAT YOU FULLY
TRUST BECAUSE THE STATISTICS OF YOUR ACCOUNT WILL BE AFFECTED BY THEIR ACTIONS,
SO THEY CAN POTENTIALLY REDUCE THE NUMBER OF BUYERS WILLING TO BID FOR YOUR CPU
RESOURCES. IF YOU DON'T FOLLOW THIS ADVICE AND YOU OFFER FOR DOWNLOAD ANY
CPUSHARE SELL ORDER OR ANY CPUSHARE LIVE CD ON THE INTERNET, YOU'RE RECOMMENDED
AT LEAST TO ASK THE THIRD PARTIES VISITING YOUR INTERNET SITE TO READ AND AGREE
WITH THE CPUSHARE USER AGREEMENT AT THE URL
http://www.cpushare.com/user_agreement BEFORE STARTING RUNNING THE CPUSHARE
SOFTWARE OR THE CPUSHARE LIVE CD OR ANY OTHER CPUSHARE RELATED DEALING. BUT IN
ANY CASE THE REDISTRIBUTION OF BOTH THE CPUSHARE SELL ORDERS AND THE CPUSHARE
LIVE CD REMAINS AT YOUR OWN RISK AND ANDREA ARCANGELI, CPUSHARE.COM, ITS
SUPPLIERS, AND THE OTHER PARTIES INVOLVED IN CREATING AND DELIVERING ALL THE
CPUSHARE SERVICES AT THE CPUSHARE.COM DOMAIN, THE CPUSHARE SOFTWARE AND THE
CPUSHARE LIVE CD, SHALL NOT BE LIABLE FOR ITS CONSEQUENCES.

CPUSHARE SHALL NOT BE LIABLE IF A THIRD PARTY STEALS YOUR BUY ORDERS OR THE
PASSWORD OF YOUR CPUSHARE ACCOUNT. IT IS YOURS RESPONSIBILITY TO KEEP ALL YOUR
CPUSHARE BUY ORDERS AND THE PASSWORD OF YOUR CPUSHARE ACCOUNT SECURE. YOU
UNDERSTAND THAT ANY OF YOUR BUY ORDERS PROVIDES UNLIMITED ACCESS TO THE FUNDS IN
YOUR CPUSHARE ACCOUNT.

The license of this software package is available in the file "COPYING" in this
same directory.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

CPUShare currently only works on the x86-64, ppc64 and x86 architectures.
ppc should work too but it's untested.

You need to run a kernel >= 2.6.12 if your object is to sell your CPU
resources and it must be compiled with CONFIG_SECCOMP=y (most distributions
ships it that way).

To verify that your kernel supports seccomp you can execute in this directory:

	python seccomp_test.py

If you see "The malicious bytecode has been killed successfully by seccomp" and
later "The seccomp_test.py completed successfully, thank you for testing."  you
made it and your kernel is working correctly.

To start the CPUShare client it's enough to run:

	./CPUShare start

You have to save the file "order.cpu" in this directory before starting
CPUShare. The file "order.cpu" is the CPUShare order that you downloaded from
the www.cpushare.com website (in the "Orders" section of your account).

With x86-64 under Debian you may need to run CPUShare under a chrooted 32bit
environment, here the details:

	https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html

The chroot isn't needed with other x86-64 distributions thanks to /lib64.

To stop CPUShare, you can run:

	./CPUShare stop

Simply adding something like this:

	su - nobody -c "/var/lib/nobody/cpushare/CPUShare start"

to your /etc/init.d/boot.local might be enough to autostart CPUShare at boot.

Networking doesn't need to be up and running when you start it. You're not
forced to run "./CPUShare stop" while shutting down your computer.

Alternatively you can start it with cron (runing "CPUShare start" once CPUShare
is already running won't hurt).

If the CPUShare protocol will change and it will require an upgrade of the
client software, you will be notified by email and the client will quit
automatically printing a message in the logs.

You'll find all the CPUShare logs in the files cpushare-*.log in this
directory, please check them if something goes wrong and then send all the
bugreports to the cpushare-devel@cpushare.com mailing list (you don't need to
be subscribed to post there).

If you modify the sell client in a malicious way, your sell price will go down
and eventually your account will be freezed.

There is already a debian package available and other distributions may follow
to make it easier to install it.

Enjoy!

Andrea Arcangeli