X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Rob <dtownrobbrown AT gmail DOT com>
Subject:  Re: setup.exe --quiet-mode
Date: Wed, 10 Sep 2008 18:02:59 +0000 (UTC)
Lines: 38
Message-ID:  <loom.20080910T174541-80@post.gmane.org>
References:  <loom DOT 20080904T183156-413 AT post DOT gmane DOT org> <48C0316C DOT F9E434A9 AT dessent DOT net> <00fc01c90f39$f4006970$9601a8c0 AT CAM DOT ARTIMI DOT COM>  <loom DOT 20080910T172329-77 AT post DOT gmane DOT org> <007101c9136b$a62b3e10$9601a8c0 AT CAM DOT ARTIMI DOT COM>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Dave Korn writes:

>   Err, that should never happen, unless you're updating from a
> several-years-old DLL.  The Cygwin DLL is intended to be backwardly
> compatible, and only rarely have their been ABI breaks.  So this aspect of
> updating doesn't get tested very often.
> 
Yes, I was testing an upgrade from a couple year old version: 1.5.12

> > I guess the obvious answer is to make sure NO cygwin related processes are
> > running when you run setup. But I was hoping it would just schedule the
> > files for replacement and do it on the next reboot.
> 
>   Well, yeh, it did do that.  But there's no mechanism to schedule all the
> postinstall scripts to not be run until the next reboot, which IIUIC is what
> would be needed here for them not to crash.

I think the safest bet for me in this case is to just kill off everything and 
run setup. Since I'll be doing this upgrade on close to 100 boxes, I've been 
trying to devise a *relatively* unattended process. 
In case it helps anyone in the future, here's a snippet of my cmd script I have 
so far:

echo off
echo This will kill all cygwin related processes and update cygwin
echo Hit CTRL-C now to abort, otherwise:
pause
c:\cygwin\bin\bash.exe --login -c "ps -la|sed 's/^I/ /'|awk '{print $4}'|grep -
v WINPID >/tmp/pids.txt" 
for /F %i in (c:\cygwin\tmp\pids.txt) DO taskkill /PID %i /F
del /F c:\cygwin\tmp\pids.txt
echo running setup...
\\fileserver\cygwin\setup-2.602.exe -q -L -l \\fileserver\cygwin -R C:\cygwin
echo Done






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