At 08:59 AM 7/25/01, Admin Mailing Lists wrote:
> > > seems like the sessions should close down quicker in the event of the
> > > client going away (if TCP knows, why doesn't popper?).
> >
> > When we've seen similar problems, it's usually because TCP does *not*
> > see that the modem connection has gone away; they may have been
> > disconnected, but the old TCP connection is hanging around. I'm not
> > sure why the situation you describe would come up.
> >
>
>usually when you try to write() or read() from a broken connection though,
>it'll generate an EPIPE, which you can check for, and close the
>connection if present..i looked through pop_send.c briefly but did not see
>this check for the fwrite() in pop_write_now()..i see the logging of an
>error, but no action for it..if i am, in fact, looking in the right place.
Indeed, looking at the code, and at my error logs, it would appear there's
a lack of action other than logging. I get multiple error messages in the
log file for the same error (EPERM -- Operation not permitted) when a
failure occurs. I suspect this relates to to the TCP session being gone.
-----------------------------------------------------------------
Daniel Senie [EMAIL PROTECTED]
Amaranth Networks Inc. http://www.amaranth.com
