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

Re: closing connections




On Wed, 7 Nov 2001, guy keren wrote:

> i would guess those connections have only been half-closed - and hence are
> still active (i.e. one side closed them, the other didn't). for the short
> term, you could run 'lsof -i | egrep <port_number>' (as root) to find
> which process on your machine holds the given port open (i know, this

lsof?  What about netstat -p ?  (I run slackware..)

> egrep is not enough, but you can sort through the few lines it gives you
> by hand) and then possibly kill that process (assuming its a forked-off
> process that only handles this single connection).

it's fetchmail..  I have it running as a daemon.

> for the longer term - you should check why this happens. could be that the
> connection closing packets are being filtered out by a packet filter along
> the path?

Not that I am aware.  Besides, fetchmail opens two connections every five
minutes on this machine and it's been up for 58 days..  there would be a
lot more then that.  Actually, at second look there are also some
connections still ESTABLISHED with bytes in the RECV queue.  Maybe I need
a newer fetchmail...  

On second thought, we have two servers and the other one doesn't pile up
connections like that as much.  Perhaps it has to do with the adsl
connection going down?  It does much more on this server than the other
one.

Anyway, thanks.  For some reason I didn't think that killing the process
would clear it all up.

-Cedar

> --
> guy
> 
> "For world domination - press 1,
>  or dial 0, and please hold, for the creator." -- nob o. dy
> 
> 




=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il