Date: Fri, 17 Aug 2001 07:44:59 -0500 From: Bob Martin <bob@buckhorn.net> To: sthaug@nethelp.no Cc: jan@digitaldaemon.com, FreeBSD-Questions@FreeBSD.org, FreeBSD-ISP@FreeBSD.org Subject: Re: Killing TCP/IP connection. Message-ID: <3B7D11CB.3728823C@buckhorn.net> References: <3B7D02DC.546A2E50@buckhorn.net> <54706.998051003@verdi.nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
sthaug@nethelp.no wrote:
>
> > > Hi, is there a way to force and end to a TCP/IP connection that shows
> > > with netstat -na ?
> > > Something like kill -HUP or -kill -TERM, but then on a socket? <g>
> > >
> > Use sockstat -4. It will give you the PID of the offending connection.
> > Then you can kill it.
>
> Unfortunately, you *don't* always want to kill the process - think of
> a server process handling many clients connections. You want to kill
> the connection to *one* client, but not the rest.
>
> Steinar Haug, Nethelp consulting, sthaug@nethelp.no
Since each connection gets it's own pid, this isn't a problem. You can
kill a single ftp session or http session without interfering with the
rest.
Bob
--
But in our enthusiasm, we could not resist a radical overhaul of the
system, in which all of its major weaknesses have been exposed,
analyzed, and replaced with new weaknesses.
-- Bruce Leverett, "Register Allocation in Optimizing Compilers"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B7D11CB.3728823C>