X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Kill cygwin process form task manager Date: Fri, 14 Nov 2008 15:00:23 +0100 Message-ID: <448067AB8643614285E9B1DC376F273C0241F884@bermail.de.aastra.com> In-Reply-To: <2ce9650b0811140323h2e620979w77118815bed87fdd@mail.gmail.com> From: "Michael Wiedmann" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id mAEE1EYp007170 Chris January wrote: > Alternatively, do it the other way round, with the child occasionally > writing to the pipe and the parent draining it. The child will get > SIGPIPE when the parent dies. This sounds great! I have already a pipe between parent and child processes for other purposes and only need to setup a signal handler for SIGPIPE. Thanks Michael -- Michael Wiedmann Software Engineer Aastra DeTeWe GmbH 10997 Berlin Germany -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/