Messages in this thread | | | Date | Tue, 18 Aug 1998 00:45:21 -0700 | From | Philippe Troin <> | Subject | Re: Sockets permanently in CLOSE_WAIT state. |
| |
Andy Sloane wrote:
> While hacking away at a project today I discovered a rather strange > occurrence in a multithreaded environment using sockets. The jist of the > problem is I was select()ing on a socket in one thread and at the same time > closing it in another (yes, this is a design oversight on my part). To my > surprise, after killing the server and all clients, the sockets remained in > the CLOSE_WAIT state, yet no client processes were still running; I > expected to at least see a thread stuck in a D state or something. It's > not a 'normal' thing to do, but it's also something that an attacker could > potentially use to run the system out of non-root sockets. Is this a known > issue? (for the record I'm using linuxthreads.)
Reread your TCP books. It's perfectly normal. Unless the sockets remain in CLOSE_WAIT more than say 15 minutes... Anyone knows the 2MSL delay in Linux ?
Phil.
- 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
| |