X-Spam-Check-By:	sourceware.org
Date:	Wed, 20 Sep 2006 20:56:36 -0700
From:	Christopher Layne <clayne AT anodized DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: simply cygwin1.dll
Message-ID:	<20060921035636.GF6790@ns1.anodized.com>
References:	<20060921032007 DOT GA6790 AT ns1 DOT anodized DOT com> <4512077D DOT 9050403 AT cygwin DOT com>
Mime-Version:	1.0
In-Reply-To:	<4512077D.9050403@cygwin.com>
User-Agent:	Mutt/1.5.11
X-Assp-Spam-Prob:	0.00000
X-Assp-Whitelisted:	Yes
X-Assp-Envelope-From:	clayne AT ns1 DOT anodized DOT com
X-Assp-Intended-For:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Wed, Sep 20, 2006 at 11:31:09PM -0400, Larry Hall (Cygwin) wrote:
> 
> Hard to say without seeing what you're seeing (insert standard plug for
> <http://cygwin.com/problems.html> here ;-) ).  The standard problem when
> doing what you're doing is forgetting to stop services.  Other than that,
> your basic description fits my modus-operandi for replacing the DLL
> manually.  So perhaps it is just your system. ;-)

One would think it were something typical like that. But I explicitly
issued a 'net stop sshd', 'net stop syslogd' and had task manager up
verifying every single cygwin related process was absolutely dead.

It wasn't until I moved the new snapshot dll out of c:\cygwin\bin and then
literally copied it back into the same directory that things worked as they
normally should. Previous to that I had just dragged (moved) the latest
snapshot dll from c:\cygwin\var\tmp\cygsnap to c:\cygwin\bin after moving
the old one out of the way (at this point all cygwin related processes
were dead). I wonder if it's a result of me renaming the new snapshot dll
to cygwin1.dll right before I exited my final cygwin shell. I would think
windows wouldn't even know that file was there yet (just sitting in some
temp directory). But I also know very little about window's behind the scenes
dll behavior.

-cl

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

- Raw text -