Andrew M. Bishop wrote:
> Felix Karpfen <[EMAIL PROTECTED]> wrote:
> > Which (if any) entries in wwwoffle.conf are worth modifying to
> > <avoid/minimise> such timeouts?
>
> The main timeout is the socket timeout. Typically this will be two
> minutes. This means that the worst case time that you will be
> connected to your ISP without any packets travelling is 2 minutes.
> Obviously if you have more than one WWWOFFLE fetch process running at
> once then the chances are that this 2 minutes time will be reduced
> proportionately.
>
> The other timeouts are the DNS timeout (usually 60 seconds) and the
> connect timeout (usually 30 seconds). Since both of these are smaller
> than the default socket timeout they will not be important.
>
This follow up is just a check-up on syntax.
Below is an extract of my latest crash:
Unusual System Events
=-=-=-=-=-=-=-=-=-=-=
Jun 10 06:01:13 eureka wwwoffles[962]: Timed out while reading from remote host.
Jun 10 06:01:15 eureka wwwoffles[959]: Timed out while reading from remote host.
Jun 10 06:01:48 eureka wwwoffles[965]: Connect fail [Connection timed out].
Jun 10 06:01:48 eureka wwwoffles[965]: Cannot open the HTTP connection to
proxy.webone.com.au port 8080; [Connection timed out].
Am I correct in reading the logged `Timed out while reading from reading
remote host' as equal to `connect time out' and the logged `Connection
timed out' as equal to `socket time out'?
Or is the story more obscure?
Felix Karpfen
--
Felix Karpfen
[EMAIL PROTECTED]
Public Key 72FDF9DF (DH/DSA)
Keyserver http://blackhole.pca.dfn.de
