From owner-freebsd-questions Mon Sep 22 21:55:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA16528 for questions-outgoing; Mon, 22 Sep 1997 21:55:56 -0700 (PDT) Received: from gdi.uoregon.edu ([128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA16523 for ; Mon, 22 Sep 1997 21:55:54 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id VAA06383; Mon, 22 Sep 1997 21:55:03 -0700 (PDT) Date: Mon, 22 Sep 1997 21:55:03 -0700 (PDT) From: Doug White Reply-To: Doug White To: Jacques Hugo cc: questions@FreeBSD.ORG Subject: Re: Killing a socket In-Reply-To: <342681CA.237C228A@wired.ctech.ac.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Sep 1997, Jacques Hugo wrote: > Hi there ... > > I don't know if this can be done ... but anyway ;) > > If I connect to a server with ssh, that server gets > my request and lets me through after the auth. > > If I kill that connection, then on netstat -a it > shows that that connection is still ESTABLISHED. > > How can I kill that socket. Is there a util to > do this or can it be done by hand? It'll die by itself when the other end realizes you've gone AWOL. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo