Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Kamen TOMOV <kamen AT cybuild DOT com>
Subject: Re: howto register process
Date: 12 Nov 2004 17:29:45 +0200
Organization: CYBUILD
Lines: 33
Message-ID: <87sm7fxeza.fsf@zlatenlist.homelinux.net>
References: <873bzfdyvh DOT fsf AT zlatenlist DOT homelinux DOT net> <NUTMEG0ApIWXzNbrDYs000006c2 AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: 212-104-100-183.cable.evrocom.net
X-Home-Page: http://www.cybuild.com
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
X-IsSubscribed: yes

On Fri, Nov 12 2004, Dave Korn wrote:

>   Waittaminnit.  You're saying that the spawned processes _aren't_
> cygwin processes?
> 
>   Well then you're entirely barking up the wrong tree.  Cygwin can't
> magically make win32 programs signal-aware.  The issue of not having
> a pid for it is utterly irrelevant.
> 
>   OTOH, I think if you were to spawn them under a shell, rather than
> by fork-and-exec, you would probably be able to kill the children by
> killing the shell, in much the same way as if you're running in bash
> and you run cmd.exe at the command line you can then kill it and
> return to the shell by pressing ctrl-c.  Which doesn't usually kill
> cmd.exe, but when it's launched as a child of a cygwin shell, works
> fine.
> 
>     cheers, 
>       DaveK
> -- 
> Can't think of a witty .sigline today....

That's a great idea. I'll stick with it and will rewrite the
application to start the daemons from the cygwin's shell. That would
make my life much easier because instead of rewriting the cygwin's
fork function to register processes in its own virtual table (although
I do not know if that is possible) they would be instantly
available. It was strange to me that fork do not make them appear
there but anyway... thank you very much!

Regards,
-- 
Kamen TOMOV


--
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/