Re: FIN_WAIT_[1,2] and LAST_ACK

From: Eli Dart (dart_at_nersc.gov)
Date: 04/05/04

  • Next message: FreeBSD bugmaster: "Current problem reports assigned to you" 
    To: Brandon Erhart <berhart@ErhartGroup.COM>
Date: Mon, 05 Apr 2004 10:17:56 -0700

    In reply to Brandon Erhart <berhart@ErhartGroup.COM> :

    > Hello everyone,

    > However, I have run into a new problem. I am getting a good amount of
    > blocks stuck in FIN_WAIT_1, FIN_WAIT_2 or LAST_ACK that stick around for a
    > long while.

    Could you define "long" in this case? Are we talking about 60
    seconds, or 60 minutes? I get the feeling that your requirements
    might make your perception of "long" different from others' notion of
    "long."

    The reason I ask is that there was a bug once upon a time that made
    some connections stick in LAST_ACK forever....

                    --eli

  • Next message: FreeBSD bugmaster: "Current problem reports assigned to you"

    Relevant Pages

    • Re: FIN_WAIT_[1,2] and LAST_ACK
      ... In reply to Brandon Erhart: ... something that needed a more general fix (see note from Mike ... do you remember how long the "problem connections" were sticking ... It doesn't switch states depending on ...
      (freebsd-net)
    • Re: FreeBSD and Debugging?
      ... > Brandon Erhart wrote: ... In the commercial arena, Rational's PURIFY and ... >> reason for this? ...
      (freebsd-hackers)