On Tue, Jul 24, 2001 at 10:38:14AM -0400, Daniel Senie wrote:
> We see occasional trouble when a user's connectivity goes south. We'll see
> the TCP session close down, but the popper process doesn't close and clean
> up. Anyone else see this? I'm still trying to track down the particulars.
>
> When it happens, users call because they've hung up the phone and redialed,
> and qpopper gives them an error since their mailbox is already in use. We
> try to explain they need to be patient and give it a few minutes, but it
> 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.
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
