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: Thu, 11 Nov 2004 13:28:39 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: howto register process Message-ID: <20041111182839.GE14312@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <87mzxoveei.fsf@zlatenlist.homelinux.net> <87vfccw8f5.fsf@zlatenlist.homelinux.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87vfccw8f5.fsf@zlatenlist.homelinux.net> User-Agent: Mutt/1.4.1i On Thu, Nov 11, 2004 at 08:24:30PM +0200, Kamen TOMOV wrote: >Thanks Dave. The thing is that the child processes get forked with a >fork() invocation. What's more not only the child pids are invisible >to cygwin, but also their parent is invisible. That is why I'm >wondering isn't there a way to make them part of the processes that >are visible by cygwin. My purpose is - to be able to kill them with >kill() and to use the signal system. Cygwin processes created with fork() and/or exec() can, of course, use cygwin signals and do show up in the process table. The Cygwin distribution wouldn't operate if this was not true. You need to provide a test case showing what you are trying to do, i.e., http://cygwin.com/problems.html . -- 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/