Date: Fri, 17 Aug 2001 14:51:41 -0500 From: Bob Martin <bob@buckhorn.net> To: sthaug@nethelp.no Cc: FreeBSD-Questions@FreeBSD.org, FreeBSD-ISP@FreeBSD.org Subject: Re: Killing TCP/IP connection. Message-ID: <3B7D75CD.6A02B579@buckhorn.net> References: <3B7D11CB.3728823C@buckhorn.net> <55978.998052757@verdi.nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
sthaug@nethelp.no wrote: > > > > 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. > I agree, but for the life of me, I can't think of a single program that does that. The ones that give me greif are things like IMAP and FTP that open a half dozen connections for one remote client. Bob Martin 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?3B7D75CD.6A02B579>