distributed.net client configuration:
--------------------------------------------------------------------------
1) General Client Options
2) Buffer and Buffer Update Options
3) Performance related options
4) Logging Options
9) Discard settings and exit
0) Save settings and exit
Choice -->2
distributed.net client configuration: Buffer and Buffer Update Options
--------------------------------------------------------------------------
1) Buffer in memory only? (no disk I/O) ==> no
2) In-Buffer Filename Prefix ==> buff-in
3) Out-Buffer Filename Prefix ==> buff-out
4) Checkpoint Filename ==>
5) Disable buffer updates from/to a keyserver ==> no
6) Keyserver<->client connectivity options
7) Disable buffer updates from/to remote buffers ==> no
8) Remote buffer directory ==>
9) Load-work precedence ==> RC5,OGR=0,CSC,DES
10) Additional buffer-level checking ==> 0 (none)
11) Buffer-level check interval ==> 0:00 (on buffer change)
12) Preferred packet size (2^X keys/packet) ==> RC5=33
13) Fetch work threshold ==> RC5=1000,OGR=10
14) Fetch time threshold (in hours) ==> RC5=0
0) Return to main menu
Make sure the packet size is 33, just because that lowers bandwidth usage (when downloading, and uploading)
Then, choose #13.
distributed.net client configuration: Buffer and Buffer Update Options
--------------------------------------------------------------------------
Fetch work threshold:
This option specifies how many *work units* your client will buffer between
communications with a keyserver. When the number of work units in the
input buffer reaches 0, the client will attempt to connect to a keyserver,
fill the input buffer to the threshold, and send in all completed work
units. Keep the number of workunits to buffer low if you have a fixed
connection to the internet, or the cost of your dialup connection is
negligible. While you could theoretically enter any number in the fields
here, the client has internal limits on the number of packets that it can
safely deal with.
A value of 0 for the 'fetch setting' indicates that a time threshold
should be used instead. If that too is unspecified, then the client will
use defaults.
* See also: 'Additional buffer-level checking'
Default Setting: 0 (default size or determine from time threshold)
Current Setting: RC5=1000,OGR=10
New Setting --> RC5=1000,OGR=10
Instead of choosing 1000 for RC5 (that's 1,000 WU's, or blocks), choose 360 * X where X is the number of days you'll be gone. To be safe, perhaps choose 400 * X (incase you're late
). You can choose OGR = 0 if you want.
Then, to make sure that it doesn't dialup on it's own, after you put in how many blocks you want (presing enter will bring you back to this screen
distributed.net client configuration: Buffer and Buffer Update Options
--------------------------------------------------------------------------
1) Buffer in memory only? (no disk I/O) ==> no
2) In-Buffer Filename Prefix ==> buff-in
3) Out-Buffer Filename Prefix ==> buff-out
4) Checkpoint Filename ==>
5) Disable buffer updates from/to a keyserver ==> no
6) Keyserver<->client connectivity options
7) Disable buffer updates from/to remote buffers ==> no
8) Remote buffer directory ==>
9) Load-work precedence ==> RC5,OGR=0,CSC,DES
10) Additional buffer-level checking ==> 0 (none)
11) Buffer-level check interval ==> 0:00 (on buffer change)
12) Preferred packet size (2^X keys/packet) ==> RC5=33
13) Fetch work threshold ==> RC5=1000,OGR=10
14) Fetch time threshold (in hours) ==> RC5=0
0) Return to main menu
Choice -->6
choose 6
distributed.net client configuration: Keyserver<->client connectivity options
--------------------------------------------------------------------------
1) Network Timeout (seconds) ==> 60 (default)
2) Automatically select a distributed.net keyserver? ==> no
3) Keyserver hostname ==> proxy.teamanandtech.com
4) Keyserver port ==>
5) Keyserver is a personal proxy on a protected LAN? ==> no
6) Firewall/proxy protocol ==> none/transparent/mapped
7) Use HTTP encapsulation even if not using an HTTP proxy? ==> no
8) Always use UUEncoding? ==> no
9) Dialup-link detection ==> Dial-up detection ONLY mode
10) Interfaces to watch ==>
0) Return to Buffer and Buffer Update Options
Choice -->9
choose 9.
distributed.net client configuration: Keyserver<->client connectivity options
--------------------------------------------------------------------------
Dialup-link detection:
0) Off: the client will send/receive packets only when it needs to do so.
1) Dial-up detection mode: This acts like mode 0, with the addition
that the client will automatically send/receive packets when a
dial-up networking connection is established. Modem users
will probably wish to use this option so that their client
never runs out of packets.
2) Dial-up detection ONLY mode: Like the previous mode, this will cause
the client to automatically send/receive packets when
connected. HOWEVER, if the client runs out of packets,
it will NOT trigger auto-dial, and will instead work
on random RC5 packets until a connection is detected.
Default Setting: 0
Current Setting: 2
New Setting --> 2
I suspect that you're on dialup, so you'll want option 2, so it won't dialup on its own while you're away.
Facebook
Twitter