Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Originating-IP:	[12.254.208.112]
X-Originating-Email:	[mgainty AT hotmail DOT com]
From:	"Martin Gainty" <mgainty AT hotmail DOT com>
To:	<cygwin AT cygwin DOT com>, =?iso-8859-1?Q?Sven_K=F6hler?= <skoehler AT upb DOT de>
References:	<b7ct02$k8g$1 AT main DOT gmane DOT org> <Law10-OE40Sv0YKpDS7000000f4 AT hotmail DOT com> <b7cv5r$pr3$1 AT main DOT gmane DOT org> <Law10-OE3577bieLYCT00000ad4 AT hotmail DOT com> <b7d10n$56i$1 AT main DOT gmane DOT org>
Subject:	Re: setup.exe and "in-use-file"
Date:	Sun, 13 Apr 2003 19:12:52 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID:	<Law10-OE49AsK6ExU8r00000a65@hotmail.com>
X-OriginalArrivalTime:	14 Apr 2003 01:13:27.0514 (UTC) FILETIME=[0DCCC3A0:01C30223]

Sven-
Sven-

What if you were to write a task yourself
The operator executes this particular task and uses your binaries to
initialise, create windows, query DB whatever..
Along comes someone who desires to change a piece of your running processes
functionality..just one DLL this person cries but your answer is that the
task is running and is currently operational and has no capacity to
understand this new functionality as the existing functionality is covered
by the DLL that was originally loaded during your Application's
Initialisation..A conflict arises..

I have not seen a Windows environment which allows new components to be
assimilated except in a Distributed Architecture..Accordingly The Cygwin
environment is decidedly not distributed but monolithic in design and in
implementation..

To put in your new DLL to replace the DLL which is currently running you
will have to find the Cygwin task that is using the DLL and kill it so the
process will release it's lock on resources that it is using...

Make Sense?

Martin

----- Original Message -----
From: "Sven Köhler" <skoehler AT upb DOT de>
To: <cygwin AT cygwin DOT com>
Sent: Sunday, April 13, 2003 5:54 PM
Subject: Re: setup.exe and "in-use-file"


> > That is considerably more difficult a task
> > You would have to code a taskwalker which identifies the Cygwin task
that is
> > running and summarily kill it
> > ..Meanwhile keeping the install dialog active waiting for the file to be
> > unlocked by the Cygwin process.
>
> i feel very misunderstood!
> i didn't want setup.exe to walk any process-tree or somethin!
> i just wanted setup.exe to retry opening the file! (after the user has
> terminated any app/service that might be still running)
>
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -