Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-Id: <3.0.5.32.20020501071246.007ca5d0@mail.attbi.com> X-Sender: phumblet@mail.attbi.com Date: Wed, 01 May 2002 07:12:46 -0400 To: From: "Pierre A. Humblet" Subject: Re: Why no shutdown? (was: Re: SSH -R problem) In-Reply-To: <006601c1f0f3$6f7df750$42a18c09@wdg.uk.ibm.com> References: <3.0.5.32.20020429205809.007f2920@mail.attbi.com> <3.0.5.32.20020429205809.007f2920@mail.attbi.com> <3.0.5.32.20020430073223.007e3e00@mail.attbi.com> <20020430142039.D1214@cygbert.vinschen.de> <3.0.5.32.20020430215517.007f13e0@mail.attbi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 10:34 AM 5/1/2002 +0100, Max Bowsher wrote: > >Why no shutdown? (I am aware that this is dangerously off-topic for >cygwin-patches. I am cross posting there only for continuities sake. Please You can only shutdown when closing the socket for good at the end of the connection, but not e.g. when a parent process closes its copy after forking a child worker. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/