* Andrew M. Bishop <[EMAIL PROTECTED]> [12.01.04 08:11]: > > There are two different types of error message that you are getting.
> > 2) Cannot write to client; disconnected? > > When WWWOFFLE was writing data to the browser the connection was > broken (by the browser) and WWWOFFLE failed to continue writing. > Possibly this was caused by pressing the "stop" button in the browser > or following a link before the page finished loading. Given the way that WWWOFFLE "fetch" works, I would have thought that "following a link before the page finished loading" is quite normal. > > > None of these errors are important unless they start occuring all of > the time > I thought them worth a posting to "wwwoffle-users" because they have recently been turning up quite frequently. > or are related to times when you expect to be getting > something from WWWOFFLE but it fails. I have a "viewing program" that sorts the logged messages into "critical" and "unususal". The flagged WWWOFFLE messages all ended up in "unusual", so I was aware that the problem is not serious. However, by the time that I look at the logs, the memory of the exact sequence of <successful|failed> lookups is starting to fade. As mentioned in my original posting, I have not been conscious of an above-average number of failed connections while actually online. But one fail may score several WWWOFFLE error messages. Thank you for the advice. Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA)
