Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After sending the STOP signal to a process, it stops working as expected, but still accepts TCP connections. So is it working anyhow?

share|improve this question
Sounds like the operating system is excepting them on your behalf, I think this happens to reduce latency. – richard Sep 27 '12 at 22:17
up vote 2 down vote accepted

Once a Unix process binds an IP address and port to a stream socket, the kernel begins accepting TCP connections for that address/port and continues until the socket is unbound or closed. The process gains access to the connections via the accept() system call, but the connections are happening regardless. Beyond the initial TCP handshake, the connection is idle until accept() is called and the process start to use the connected socket.

So connections are occurring but there isn't any real activity (mail being sent, web pages being served, etc.) while the process is stopped.

share|improve this answer
Sounds plausible. Just wanted to add there is activity. Data sent to the process over the connection is acknowledged. – Holy Sheet Sep 28 '12 at 7:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .