Not about toilets RE: Re: [RC5] ???
cloacasoft at hotmail.com
Sun Mar 10 22:23:24 EST 2002
Mine does this anyway. What settings did you change? Set fetch
threshold to 0 (dnetc -config | 2 | 13 | enter "RC5=0,OGR=0") and
connectivity to normal (dnetc -config | 2 | 6 | 7 | enter "0") and you
should be fine. I don't see any flush threshold in the client, though
the personal proxy does have that setting if that's the sort of thing
that you're in to.
From: owner-rc5 at lists.distributed.net
[mailto:owner-rc5 at lists.distributed.net] On Behalf Of Deák Krisztián
Sent: Sunday, March 10, 2002 4:44 PM
Subject: Re: [RC5] ???
Haven't posted here before, but since only toilets are being discussed
at the moment, I don't feel that I'm interrupting some deeply scientific
debate by asking:
How can I setup the client to send every completed block (or at least
not wait until the in-buffer is exhausted)? I've recently switched to a
cable connection from a modem/dial-up setup. Before, I knew I was
sending all completed work when I connected to the Internet, but now I
see my stats show no work completed until I start the client with
This is the Windows client, if that makes any difference.
To unsubscribe, send 'unsubscribe rc5' to
majordomo at lists.distributed.net rc5-digest subscribers replace rc5 with
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
More information about the rc5