listening socket alive even after process death ?
Date: 08/16/05

Date: 16 Aug 2005 14:01:03 -0700

I have a program (prog#1) that listens for TCP connections on port
37708 on host host#1.
Many other processes (prog#2) connect and communicate with it from a
variaty of other hosts.

I kill listening program on host#1 with SIGINT.
All prog#2's are still in select waiting to get something from prog#1.
Sockets seem to be all alive on the other end although listening
program have died.

Moreover I can even connect to host#1 on the same port with telnet.

netstat -p -n --inet
shows lines like:
tcp 23 0
tcp 23 0
Last column is supposed to show PID of the process but it actually is
just dash.

How can this be that process have died and it's sockets didn't ?

>Linux 2.4.21-20.ELsmp #1 SMP Wed Aug 18 20:34:58 EDT 2004 x86_64 x86_64 x86_64 GNU/Linux


Relevant Pages

    ... Yes the host is listening on port 3389 the default and I verified this. ... Try connecting again. ...
  • Re: security risk of having a long list of services in inetd
    ... for connections on certain internet sockets. ... the string 'ssh' means TCP port 22. ... But if there's no program sitting there listening on the port there's ...
  • Re: nessus report
    ... when i ran nessus against my bsd box, nessus can detect "the remote host ... There are several ways to detect if a host is up. ... Sometimes services will respond differently if they're firewalled than if they're not listening on a particular port. ...
  • Re: blocking sockets?
    ... The server handles requests and spawns a child process for every connection. ... If a client sends the text "foo" to the server, the server itself should try to make a connection with another service on port 4321. ... The parent process should still be listening on port 1234 if you have actually spawned a child process to read and write data from the remote client,. ... Non-blocking sockets. ...
  • Re: Socket bind: Port-Wiederverwendung
    ... Port anzugeben, ... Sockets schon wieder freigegeben habe, ... Es muss wirklich immer der gleiche Host sein! ... Das .Net Framework stell entsprechende Klassen zur ...