Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 22 Sep 2005 16:02:23 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: CTRL-C kills ALL processes, not just foreground process. Message-ID: <20050922200223.GC10392@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050922194738 DOT GB10392 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050922194738.GB10392@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i On Thu, Sep 22, 2005 at 03:47:38PM -0400, Christopher Faylor wrote: >On Thu, Sep 22, 2005 at 03:36:38PM -0400, Joe Smith wrote: >>"Big Action" wrote: >>>Do I only need to replace the cygwin1.dll, or should I download and >>>extract the entire "make install" tree? >> >>replace the cygwin1.dll I would recomend rebooting afterwards before >>testing just to be sure everything is using the new version. > >You can't replace a running DLL so this should be unnecessary. If you >can overwrite cygwin1.dll with a new version then you should be all set. >If this wasn't the case, I'd be rebooting all day long. I don't know if the above is clear or not but what I was trying to say was that if anything else was using cygwin1.dll, you wouldn't be able to copy over it. You *have* to stop all running cygwin processes before replacing cygwin1.dll so, given that, there is no reason to reboot if you have successfully managed to copy over, e.g., c:\cygwin\bin\cygwin1.dll . cgf -- 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/