RC5: not submitting blocks??

[Deceiver]

I recently downgraded to another version because of problems with the newest version that distributed had on their site. I'm now running version 463. I kept the same ini file I had from before, but now my blocks aren't being submitted every so often. The 3rd I had only a small amount submitted from a another computer that already had the older version. I went to check my own computer, and it had a whole bunch of blocks that hadn't been sent. I decided to do a flush, and so my stats for the 4th are way up. I've also checked today and none of my blocks from last night have been sent. What determines how often RC5 sends in the blocks? I have it set to receive 72 hrs worth of work, although I'm connected to the net 24/7.

Here is my ini file
[parameters]
id=jrw@umr.edu

[display]
progress-indicator=on

[networking]
keyserver=proxy.teamanandtech.com
nofallback=true
autofindkeyserver=no
dialup-watcher=passive
interfaces-to-watch=*

[misc]
run-work-limit=0
project-priority=RC5,OGR,DES,CSC

[rc5]
fetch-time-threshold=24
preferred-blocksize=33

[buffers]
checkpoint-filename=cp
frequent-threshold-checks=3

[triggers]
restart-on-config-file-change=yes

[ogr]
fetch-workunit-threshold=2

Thanks for the help..

 

[mechBgon]

Is that computer on a dial-up connection? If so, you can set it up for automatic dial-out when it needs to fetch and flush:

dialup-watcher=active

If it's on a constant connection, try adding this under [buffers]:

threshold-check-interval=0:30

Let us know how it goes, ok? I don't have a dial-up connection to test my recommendations with but those are some educated guesses. 🙂

edit: let me add that you will want to use the client's configuration menu to specify a dial-up connection for the client to use:

distributed.net client configuration: Keyserver<->client connectivity options
--------------------------------------------------------------------------
1) Network Timeout (seconds) ==> 15
2) Automatically select a distributed.net keyserver? ==> no
3) Keyserver hostname ==> 24.9.201.178
4) Keyserver port ==> 2064
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 mode
10) Interfaces to watch ==>
11) Use a specific DUN profile to connect with? ==> no

Switch 11 to &quot;yes&quot; and then you will be able to chose a dial-up connection for it to try.

 

[Deceiver]

No, I'm on a cable modem 24/7. I added that line, so I'll see how it goes. Does this line check the buffers and submits them every 30 minutes?

 

[mechBgon]

That's right.

 

[Russ]

The line that was causing the problem is:

fetch-time-threshold=24

That tells it to update (fetch and flush) only every 24 hours.

Russ, NCNE

 

[Deceiver]

cool, thanks. i've set it to 0:30