lkml.org 
[lkml]   [1998]   [Aug]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Sockets permanently in CLOSE_WAIT state.

    I've seen this happen with 2.0.32.. They are still stuck today, over a
    month later.

    On Tue, 18 Aug 1998, Andy Sloane wrote:

    > On Tue, Aug 18, 1998 at 12:45:21AM -0700, Philippe Troin wrote:
    >
    > > Reread your TCP books.
    > > It's perfectly normal. Unless the sockets remain in CLOSE_WAIT more than say
    > > 15 minutes...
    >
    > I'm well aware of the purpose of the CLOSE_WAIT state.
    > tcp 1 0 aikon.incarnate.n:30687 aikon.incarnate.n:31337 CLOSE_WAIT
    > tcp 1 0 aikon.incarnate.n:30655 aikon.incarnate.n:31337 CLOSE_WAIT
    > tcp 1 0 aikon.incarnate.n:30625 aikon.incarnate.n:31337 CLOSE_WAIT
    > tcp 1 0 aikon.incarnate.n:30562 aikon.incarnate.n:31337 CLOSE_WAIT
    > tcp 1 0 aikon.incarnate.n:30501 aikon.incarnate.n:31337 CLOSE_WAIT
    >
    > These five sockets have been stuck in their state for about five
    > hours now, and the process that controls them has been dead for as long.
    > I've gone over my process list several times looking for the offending
    > threads.
    >
    > -Andy
    >
    > -
    > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    > the body of a message to majordomo@vger.rutgers.edu
    > Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
    >


    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

    \
     
     \ /
      Last update: 2005-03-22 13:44    [W:0.026 / U:60.360 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site