Changes between Version 8 and Version 9 of CPUShare


Ignore:
Timestamp:
04/05/2008 01:01:27 PM (16 years ago)
Author:
Sam Hocevar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CPUShare

    v8 v9  
    1616== What happens exactly? ==
    1717
    18 Your machine's idle CPU cycles will be available on the CPUShare platform. The CPUShare daemons run at a very low priority (`nice -19` by default) but you can stop the daemon at any time if the impact on your system is too important.
     18Your machine's idle CPU cycles will be available on the CPUShare platform. The CPUShare daemons run at a very low priority (`nice -19` by default) but you can stop them at any time if the impact on your system is too important.
    1919
    20 There is no way to know whether your CPU will be always used for libcaca projects. However, because you use our `.cpu` file, the CPUCoins earned by running CPUShare software will be credited to the libcaca project's account. We will in turn use these CPUCoins to buy CPU cycles on other machines; maybe yours, maybe not.
     20There is no way to know whether your CPU will only be used for libcaca projects. However, because you use our `.cpu` file, the CPUCoins earned by running other software will be credited to the libcaca project's account, too. We will in turn use these CPUCoins to buy CPU cycles on other machines; maybe yours, maybe not.
    2121
    2222If you do not like giving CPUCoins directly to the libcaca project, you can create your own `.cpu` file by creating an account on [http://www.cpushare.com/ cpushare.com] and [https://www.cpushare.com/orders/ creating a new sell order].