Something is screwy with my D.net client?

[Imported]

Lately, my D.net client has been flushing automatically even though it's not set to it. I remeber in December, it flushed around 45k in the middle of the night, last month it did 30k, then 4 days ago it flushed around 2300, and just today 1455. Why is it doing that? I have it set to where it won't flush automatically.. but I guess it seems to be ignoring that now.

 

[Jator]

Post your ini file and the client version, then we will be able to diagnose this mystery.

 

[Imported]

[parameters]
id=rc5@tacube.com

[buffers]
checkpoint-filename=cp

[rc5]
preferred-blocksize=33
fetch-workunit-threshold=15000
core=6
randomprefix=254

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

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

[networking]
autofindkeyserver=no
keyserver=207.108.218.138


This client was the ready to go one for TA Cube, 24/7 and broadband or something. Don't remember the whole thing.

 

[Jator]

Are the buffers empty when it flushes? Right now, it will flush/fetch when it's out of blocks.

Jay

 

[Viztech]

I think that you are reaching the 500 packet limitation (500x32=16,000 max total WUs)

If you are getting smaller than the 2^33 size (32 WU packets) then you will automatically flush when it has finished the work in the in-buffer.

viz

 

[Imported]

Buffers are full.