X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4D995AA9.9090909@gmail.com> References: <4D995AA9 DOT 9090909 AT gmail DOT com> Date: Mon, 4 Apr 2011 08:39:56 +0100 Message-ID: Subject: Re: Utility: injob From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 4 April 2011 06:44, Daniel Colascione wrote: > Attached is a small program that runs a set of processes under an NT job > object, allowing you to stop, resume, and kill them using normal Cygwin > job control --- whether or not these processes are Cygwin programs. Very nice. One issue I frequently see with mintty (and any other pty-based terminal) is with trees of native processes, e.g. a Visual Studio build through vcbuild. ^Cing it in mintty kills the top process point blank (via TerminateProcess), which means its child processes continue to run. Your utility appears to address that. Could its approach be used in the Cygwin DLL? Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple