Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

stay socket


Actually the socket is in a ESTABLISHED state. And yes it's causing a
problem in that a remote server
program is sending messages to the wrong socket.  So there is data in the
recv-q (about 9k) but the
process that created the socket is no longer running.  I know what program
opened it and it is not running.

I tried using "netstat -p" to get the PID 'just to be save' but netstat
segfalted when using the -p option.

I have managed to kill the socket in a rather brute force method of pulling
the ethernet cable and cycling the network
sub-subsystem.  But it's not the appoach if this occures in the field.


Frank Ramsay
Systems Programmer
Castel, Inc
100 Cummings Center
Suite 157h
Beverly, MA 01915
(978) 236 1000 (voice)
(978) 236 1197 (fax)
Email: framsay at

|         |           kclark at CetaceanNe|
|         |  (Kevin|
|         |           D. Clark)        |
|         |                            |
|         |           03/31/2003 12:27 |
|         |           PM               |
  |                                                                                                                              |
  |       To:       FRamsay at                                                                                         |
  |       cc:       discuss at                                                                                              |
  |       Subject:  Re: stay socket                                                                                              |

FRamsay at writes:

> I have a socket showing up on netstat for a process that is no longer
> running.  Is there any command line way to force this socket to close?
> (short of re-booting).

Very precisely speaking, what are you trying to accomplish by doing
this?  Is this actually causing a problem?

Let me guess:  this is a TCP socket in the TIME_WAIT state?

Kevin D. Clark / Cetacean Networks / Portsmouth, N.H. (USA)!kclark (GnuPG ID: B280F24E)!kdc

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /