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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: rebaseall (was Re: Perl Win32::Shortcut screws up fork)
Date: Thu, 14 Jul 2005 16:28:42 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <42D67DFC.4040205@familiehaase.de>
Message-ID: <SERRANOf4DHLZG6Ddqj00000553@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Gerrit P. Haase
>Sent: 14 July 2005 16:00

> Dave Korn wrote:
>>> On Mon, Jul 11, 2005 at 11:50:08PM -0400, Christopher Faylor wrote:
>>> 
>>>> OTOH, writing a mingw C program to do what rebaseall does wouldn't be
>>>> *that* hard.
>>> 
>>> Agreed.
> 
>>   Once again, let me point out -- that will not solve the problem.  You
>> won't be able to run the mingw executable from bash, for obvious
>> reasons.......
> 
> Isn't it possible to identify all cygwin processes, terminate them and
> do stuff after that is finished, even if the process was started at the
> bash prompt?

  Absolutely.  It should look for cygwin services as well.  I was thinking
of having a go at it in the next week or two.  I was also wondering whether
really it shouldn't be part of setup.exe (which I think came up in
discussion on -apps recently, but I wasn't following closely - have to go
check the archives).

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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