Broken Pipes with b17

From: Clemens Martin <martin@dont-contact.us>
Date: Tue, 25 Jun 1996 22:59:59 +0000

We have quite a lot of these in our cache.log

) Broken pipe.
[25/Jun/1996:22:44:25 +0100] comm.c:379: connect:
194.163.250.34:8080: ( 32) Broken pipe. [25/Jun/1996:22:44:44 +0100]
comm.c:379: connect: 194.15.144.7:8080: (32 ) Broken pipe.
[25/Jun/1996:22:45:25 +0100] comm.c:379: connect:
194.15.144.7:8080: (32 ) Broken pipe. [25/Jun/1996:22:45:25 +0100]
comm.c:379: connect: 194.15.144.7:8080: (32 ) Broken pipe.
[25/Jun/1996:22:45:25 +0100] comm.c:379: connect:
194.163.250.34:8080: ( 32) Broken pipe. [25/Jun/1996:22:45:33 +0100]
comm.c:379: connect: 194.163.250.34:8080: ( 32) Broken pipe.
[25

where the adresses are our parents running the same b17 as
we do.

The result seems to be that our users get some kind of access
denied messages in there browsers.

Could anyone comment on this. Can one increase timeouts or
such?

Cheers

C. Martin
-----
Clemens Martin ebner & martin informationssysteme gmbh
Email: martin@arkaden.net fon 089 69370145
WWW: http://www.arkaden.net/ fax 089 69370146
Bruennsteinstr. 5, D-81541 Muenchen fon 02131 911286
Furtherhofstr. 1, D-41462 Neuss fax 02131 549147
--Internet Service Center fuer IS Internet Services GmbH & Co --
Received on Tue Jun 25 1996 - 14:11:32 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:32:32 MST