Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Tue, 10 May 2005 11:38:38 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: problems in Perl process management Message-ID: <20050510153838.GA15665@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <55E0A3E94323974F83CFC5AAB96F68B801418A0B AT snnexc03 DOT in DOT ce DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Tue, May 10, 2005 at 01:12:05PM +0200, Jurgen Defurne wrote: >I also would like to know if it is possible. > >However, it could be that it has nothing to do with Cygwin. I have >a Perl script which forks several children and monitors their output. > >If a child fails, then it has no use to run all forked processes further >and I kill them with the perl 'kill' command. However, I also notice that >deeper forked processes (grandchildren) refuse to die. This >script is only run using ActiveState Perl. ActiveState perl is a windows program. You can't send cygwin (aka unix) signals to a windows proram. >I think it is really a serious Windows problem, because using >the task manager it also seems not really possible to kill a complete >process hierarchy. XP has an option for killing the process hierarchy. Just right click on the process. cgf -- 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/