From owner-freebsd-questions Fri Aug 17 5:52:44 2001 Delivered-To: freebsd-questions@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 2539537B405 for ; Fri, 17 Aug 2001 05:52:40 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 55980 invoked by uid 1001); 17 Aug 2001 12:52:37 +0000 (GMT) To: bob@buckhorn.net Cc: jan@digitaldaemon.com, FreeBSD-Questions@FreeBSD.org, FreeBSD-ISP@FreeBSD.org Subject: Re: Killing TCP/IP connection. From: sthaug@nethelp.no In-Reply-To: Your message of "Fri, 17 Aug 2001 07:44:59 -0500" References: <3B7D11CB.3728823C@buckhorn.net> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 17 Aug 2001 14:52:37 +0200 Message-ID: <55978.998052757@verdi.nethelp.no> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > 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. > > 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. 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. 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