Hi,
I'm not sure exactly where we record the time of last activity so it is possible the length of time between commands is an issue.
Another possibility is DNews isn't sending anything for the timeout period of the client (Around 2 minutes in OE), causing the client to timeout rather than the server.
This can be caused by the time taken to build the xover database if your system is busy (Clients usually request xover which is a single transfer of summary information on the group content). The xover data is built when the first user reads the group, so subsequent reads should be much faster.
There are of course other possibilities, in particular firewalls and network related issues that could also result in simialr behaviour.
If you're concerned, I suggest using the output of 'tellnews stats' to see if DNews has been spending a lot of time on disk IO and xover. This may indicate system load is the problem.
- Roydon L.
[EMAIL PROTECTED] wrote:
Hello, One of my customers was downloading headers from a large group today when his NNTP software reported a time-out waiting for a response from DNEWS. Based on the time he gave me, I believe this is the relevant section of the DNEWS log:
22 17:02:55 :warn: chan: Closing idle channel 0, idle for 3601 seconds limit 3600
My interpretation: the customer was on a slow connection & tried to download all headers for a large group (200K+ articles). His NNTP client had made 60 minutes worth of progress when DNEWS terminated the connection as "idle." I.e., "idle" meant "no new commands in the last hour," despite the one being processed.
Am I getting this right? I would like to understand if this behavior is by design.
Thanks, Gordon (DNEWS version 5.7b1)
