Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Fri, 9 Nov 2001 15:02:02 +0100
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: sshd dies
Message-ID: <20011109150202.C1099@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <7e DOT 1d9b2db3 DOT 291d2423 AT aol DOT com> <3BEBD2E6 DOT 3767C378 AT syntrex DOT com> <20011109143332 DOT B1099 AT cygbert DOT vinschen DOT de> <3BEBDF05 DOT B968A730 AT syntrex DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3BEBDF05.B968A730@syntrex.com>; from ptsekov@syntrex.com on Fri, Nov 09, 2001 at 02:49:57PM +0100

On Fri, Nov 09, 2001 at 02:49:57PM +0100, Pavel Tsekov wrote:
> Corinna Vinschen wrote:
> > 
> > On Fri, Nov 09, 2001 at 01:58:14PM +0100, Pavel Tsekov wrote:
> > > GregHolmes AT aol DOT com wrote:
> > > >
> > > > After updating Cygwin this morning (~6:30 EST 11/9) I can't seem to run sshd.
> > > >
> > > > $ /usr/sbin/sshd
> > > > D:\CYGWIN\USR\SBIN\SSHD.EXE: *** MapViewOfFileEx 'shared'(0x20), Win32 error
> > > > 8.
> > >
> > > This is ERROR_NOT_ENOUGH_MEMORY. And maybe relates to this comment in
> > > MSDN - though
> > > this is just a hypothese.
> > 
> > Or, perhaps, didn't you stop sshd before updating?
> 
> 
> Good point :) Quite, strange error code though :)
> 
> 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.

This is a 9x/Me only problem anyway.  On NT setup.exe tells you that
the dll can't be overwritten.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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