[RC5] Client buffer updates on DSL

Dan Petrak dpetrak at fct.com
Fri Mar 30 12:56:54 EST 2001

Thank you.  At least now we know you're using a new[er] version of the
client as well...

It would help even more if you could tell us if the client is even
ATTEMPTING to go and fetch more blocks or not.  [My apologies if your
original posting weeks ago had this information, I don't keep much of the
discussion groups for very long.]

If it is not attempting to update the buffers at all, perhaps try deleting
all three options under [networking] and restart the client.

[I'm also assuming you don't have a [triggers] section which could
automatically restart the client upon config changes...  I have to assume
this since you didn't mention that it was one of the things you left out.]

Daniel C. Petrak
Senior System Administrator
The FCT Group of Companies
This e-mail message and the information it contains are confidential and are
intended solely for the use of the intended addressee(s).  Any unauthorized
disclosure, use or dissemination, either whole or in part, is prohibited.
If you are not the intended recipient(s) of the message, please notify the
sender immediately by e-mail reply.

-----Original Message-----
From: Rodney R. Korte [mailto:rkorte at psu.edu] 
Sent: Friday, March 30, 2001 12:02 PM
To: rc5 at lists.distributed.net
Subject: RE: [RC5] Client buffer updates on DSL

On Fri, 30 Mar 2001 11:33:12 -0600, Dan Petrak wrote:

>I would recommend posting the entire .ini file and just blanking out 
>what you don't want people to see.  There may be other things in there 
>which do not seem relevant to you, [especially since you don't have a 
>properly functioning client] but do in fact affect the operation of the 

I seriously doubt that my id, randomprefix, project priority, display and
logging options affect the fetch.  The remainder is what I posted. (The ini
files are not as extensive today as they were with the first clients 3 years
ago.  Of course, the options are not all documented as they used to be

Can someone confirm or deny that the way I've outlined that I want the the
client is actually possible?

>-----Original Message-----
>From: Rodney R. Korte [mailto:rkorte at psu.edu]
>Sent: Friday, March 30, 2001 11:10 AM
>To: rc5 at lists.distributed.net
>Subject: Re: [RC5] Client buffer updates on DSL
>On Thu, 29 Mar 2001 17:35:03 -0800, Frank Schickel wrote:
>>   When I set the client options to watch all connections and make 
>>there's always work available.  When I went in this morning, I found 
>>that it had completed the in buffer and then worked on random blocks 
>>for the rest of the night.
>I also have problems with this, as I reported at least a couple of
>weeks ago.  A couple of people suggested some settings, but they have not
>worked for me.  My .ini file has the following (what is shown is not the
>whole thing, only the relevant sections):
>I have tried "interfaces-to-watch" equals lan*:eth*:ppp* (as someone 
>suggested, but that did not seem to work either.  However, the client
>*never* fetches automatically, even when it is doing random blocks. I
>*always* have to update manually, and thus the high block count.
>Can someone comment on something that might actually work.  I want the 
>client to fill the buffers when it can whenever the buffers reach some 
>low-tide mark.  (Whenever any interface is up and it shouldn't cause an

Rodney R. Korte
Applied Research Laboratory
The Pennsylvania State University
rkorte at psu.edu  Voice: 814-863-0817  Fax: 814-865-7303

To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest

More information about the rc5 mailing list