Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3BEBDF05.B968A730@syntrex.com> Date: Fri, 09 Nov 2001 14:49:57 +0100 From: Pavel Tsekov X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: sshd dies 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> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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. -- 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/