fischli wrote:I don`t know if this is an issue for the beta version threat. But I have never seen this error message before
"HIGH - DG - Connect Flood Delay Active: xxxNews 26 secs Remaining before Reconnect"
:o, only now in 6.30b4.
I just noticed it in 6.30B6; I started newsbin, I opened a group, it started d/l headers for the first group, then it did this 22 seconds waiting before it would d/l headers for the next group..? I have 12 connections set in the servers list for this server (my only server, giganews), I could probably bump it up to 20 or 40 or something, but it doesn't seem like its a problem hitting the max # of connections, more of... i dunno, I understand the delay to avoid connect flood, but I thought one of the things we were trying to do was use a number of connections at the same time, so we wouldn't have to wait for one thing to get done to do another... like wait for the headers in one group to d/l, then wait, wait, hold on - wait, ok, let's d/l the next group...
Not complaining, just observing what I consider odd behaviour.. perhaps the 'connect flood' you're avoiding is opening the 12, or 20, or however many connections to the server at once, and if I just held on to my panties and all the connections connected, then everything would be cool & I wouldn't notice anything? ;o
BTW - I was looking at the logging tab, because even though in the options/advanced I had logging set to 'normal', it kept showing debug level. I just set it to verbose, then 'ok', 'save configuration', then back to options/advanced, logging to 'normal' (again), 'ok', save configuration. Perhaps an old setting in the .nbi file that I've used since forever? how long? for. ever. :) But hey, at least my logging isn't out of control anymore, for what its worth..
b