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
|
distributed.net client for the unix family
document revision $Id: readme._ix,v 1.10 2008/12/30 13:24:41 andreasb Exp $
Welcome to the distributed.net client.
This document covers information specific to the client for *ix.
Refer to other enclosed documentation or browse the online FAQ at
http://faq.distributed.net/ for non-platform-specific documentation.
1.0 Getting started
2.0 *ix specific notes
1.0 Getting started ------------------------------------------------
Just unpack/unzip/untar the client in a directory of your choice and
fire it up.
If you have never run the client before, it will initiate the
menu-driven configuration. Save and quit when done.
Then, simply restart the client. From that point on it will use the
saved configuration.
The configuration options are fairly self-explanatory and can be run
at any time by starting the client with the '-config' option.
A list of command line options is available by starting the client
with '-help' or '--help'.
A complete step-by-step guide to running your first client is
available at: http://www.distributed.net/docs/tutor_clients.php
2.0 Notes: ---------------------------------------------------------
Beginning with v2.7101, the client's default directory is the
one the configuration file is located in, which in turn is assumed to
be in the same directory the binary is in (if the binary was started
with an explicit path spec). To specify another configuration file
use the -ini switch.
Beginning with v2.7102, multi-threaded clients can be forced to run
single-threaded by setting the number of CPUs (the numcpu= option in
the configuration file or the -numcpu switch on the command line) to
zero.
Also beginning with v2.7102, the restriction on the number of processors
has been lifted. The client will run with as many processors as are
available (the client will attempt autodetection if numcpu is -1). If
your client does not support processor or processor-count autodetection
and you know how to accomplish this on your platform send a code snippet
to <coders@distributed.net>
Also (herewith officially) beginning with v2.7102, the client is always
nohup'able. Sensibly enough, -HUP causes a restart. Beginning with this
release, *nix'ish clients also support -hide/-quiet mode. User level
'>/dev/null &' is deprecated, since it does not allow the client to warn
the user when it fails to start. With -hide/-quiet you can be sure that
the client has started successfully if you do not get a message to the
contrary.
Beginning with v2.7110.442, the process name (as seen from ps or top) is
uniform 'rc5des'/'dnetc'. This is to facilitate scripted or system-wide
--pause, --unpause, --shutdown and --restart
As of November 7th, 1998, much of the client source, including all the
core crunch code that was previously scattered about, is available
online at http://www.distributed.net/source/
|
