Messages in this thread | | | Subject | Re: Sockets permanently in CLOSE_WAIT state. | From | Andi Kleen <> | Date | 18 Aug 1998 20:43:08 +0200 |
| |
In article <19980818040934.B1205@aikon.incarnate.net>, Andy Sloane <andude@guildsoftware.com> writes: > 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.
Could you supply a short test case that triggers the bug? That would great help in debugging.
-Andi
- 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
| |