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 Date: Tue, 10 May 2005 23:31:27 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: problems in Perl process management Message-ID: <20050511033127.GA17813@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <55E0A3E94323974F83CFC5AAB96F68B801418B6A@snnexc03.in.ce.com.au> <20050511032249.GA17590@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050511032249.GA17590@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i On Tue, May 10, 2005 at 11:22:49PM -0400, Christopher Faylor wrote: >On Wed, May 11, 2005 at 01:19:14PM +1000, Sonam Chauhan wrote: >>Hi Christopher - >>your response to Jurgen had mentioned: >>> ActiveState perl is a windows program. You can't send cygwin (aka unix) >>> signals to a windows proram. >>This should be possible if the ActiPerl Windows executable was executed from >>a Cygwin terminal -- 'ps' shows it running and 'kill -9' should kill it. > >I guess I forgot my signature. Actually, let me clarify without being flip. Yes, if you send a "kill -9" to a pid that shows up in ps but is associated with a non-cygwin process, it should work. Other non-terminating signals will not work, and a blockable terminating signal like SIGTERM won't work. If you try to send any kind of signal to the windows pid, it won't work. I'm sorry that I wasn't entirely clear in my original reply. -- Christopher Faylor spammer? -> aaaspam@sourceware.org Cygwin Co-Project Leader aaaspam@duffek.com TimeSys, Inc. -- 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/