Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Fri, 9 Nov 2001 11:13:35 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: setup.exe suggestion [ptsekov AT syntrex DOT com: Re: sshd dies]
Message-ID: <20011109111335.E24506@redhat.com>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.21i

It probably would be a good idea to add an "is cygwin running?" check
to setup.exe.  It could be a little tricky to determine, though, since
the name of the shared regions that cygwin uses can change.

I'm sort of loath to add a standard named entity in cygwin just to
accomodate setup.exe.

Possibly, just walking through all of the processes and seeing if they've
loaded cygwin1.dll is a brute force approach.

cgf

----- Forwarded message from Pavel Tsekov <ptsekov AT syntrex DOT com> -----

From: Pavel Tsekov <ptsekov AT syntrex DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: sshd dies
Date: Fri, 09 Nov 2001 14:49:57 +0100

However, this is not why I post this message. This problem -
updating while cygwin service is running - seems to be a common
one. So it would be good if there is some mechanism that anyone
can use to see if the cygwin1.dll is active in memory. This
way setup will know that its not a good idea to run and will
inform the user that he/she must stop all the services and then
try again. 

A simple way to do this is creating a named Mutex and checking if it
exists - though I'm not sure it will apply to cygwin1.dll as easily.
But there are others too, for sure.

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

----- End forwarded message -----

-- 
cgf AT redhat DOT com                        Red Hat, Inc.
http://sources.redhat.com/            http://www.redhat.com/