Date: Fri, 17 Aug 2001 10:06:39 -0300 (ART) From: Fernando Gleiser <fgleiser@cactus.fi.uba.ar> To: <FreeBSD-Questions@FreeBSD.ORG> Cc: <FreeBSD-ISP@FreeBSD.ORG> Subject: Re: Killing TCP/IP connection. Message-ID: <20010817095635.E9633-100000@cactus.fi.uba.ar> In-Reply-To: <55978.998052757@verdi.nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 Aug 2001 sthaug@nethelp.no wrote: > That's fine for the one process per client case. But I'm talking about > the general case where *one* process handles the connections to many > clients, and you specifically *don't* have a separate process per client. > In such cases it would be very useful to have a command line facility > to kill *one* connection without interfering with the other connections > handled by the same process. If you are using TCP and the clients are on a remote machine, there is no standard way to shutdown a connection from an external process. You would need to sniff the net to know the sequence numbers involved and then send a RST. What you can do is modify the server to use some kind of IPC in which you tell it "I want to shutdown the socket connectod from ip,port to ip,port" and the server then shutown(2)s the socket. Fer > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010817095635.E9633-100000>