> > 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.
-Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
[EMAIL PROTECTED] Intergrafix Internet Services
"Dream as if you'll live forever, live as if you'll die today"
http://www.asteroid-b612.org http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
> I think we've actually seen less of this since we upgraded to
> 4.0.2/3, though I couldn't swear to it. I'm not sure why the situation
> you describe would come up.
>
> -- Clifton
>
> --
> Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED]
> WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
>
