(E-Mail Removed) wrote:
> I have a little ssh port-forwarding going on for a solution I am
> running. Most of the time, it works great, but occasionally, I get a
> "peer closed connection" error and I have to start over again. The
> interrupted connection hangs around in CLOSE_WAIT and I don't want to
> wait. I know the port connection is gone and the process that had the
> port open is killed, but it seems I have to wait for the CLOSE_WAIT to
> time out. I'sd be great if there was a way to kill the CLOSE_WAIT
> socket immediately just like I can kill the process. Does anyone know
> how I can do this? I'm tired of waiting for these connections to
> clear...
>
> /usr/ceo
You need to close the connection. The exact issue is not particular
easy to detect, but it could be as simple as calling 'fork' to fork off
a process to handle the connection but forgetting to close the
connection in the parent.
DS