Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From: ericblake AT comcast DOT net (Eric Blake)
To: "Williams, Gerald S (Jerry)" <gsw AT agere DOT com>, cygwin AT cygwin DOT com
Subject: Re: SETUP: In-use files have been replaced
Date: Tue, 18 Oct 2005 18:04:35 +0000
Message-Id: <101820051804.23742.43553933000A75E000005CBE22007614380A050E040D0C079D0A@comcast.net>

> Every time I update the cygwin package, I get a warning that in-use
> files have been replaced and that I should reboot. I assume this is
> caused by a Cygwin service, although at one point somebody on this
> list (I think it was Corinna) said that SETUP stops these services
> automatically. So I'm assuming my situation isn't normal.

Your situation isn't normal because you didn't stop all cygwin
services.  While the idea has been tossed around on this list
that it would be nice if setup.exe could stop services for you,
to date, it does not.  Therefore, IT IS UP TO YOU to stop services
beforehand.  Or provide a patch so that setup.exe can do
it for you (and for the rest of us).

I use this handy little script on my machine to help me stop
(and restart) all services:

$ cat serv
#!/bin/bash
usage='serv: manage cygwin services during cygwin upgrades
usage: serv {--help|--stop|--start}'

case $# in
1) case $1 in
  --help|-h) echo "$usage"; exit 0 ;;
  --stop) for service in `cygrunsrv --list` inetd ; do
      echo "stopping $service"
      cygrunsrv --stop $service || echo "problems with $service" ;;
    done ;;
  --start) for service in `cygrunsrv --list` inetd ; do
      echo "starting $service"
      cygrunsrv --start $service || echo "problems with $service"
    done ;;
  esac ;;
*) echo "$usage"; exit 1 ;;
esac

> I've been working around this by carefully updating only the base
> cygwin package and rebooting before updating the rest. Whenever I
> forget to do this, post-install scripts generally fail and I have
> to clean up by running them manually, etc.

That is a reasonable solution (in that you at least guarantee that
you have the latest cygwin before any other new package
postinstall tries to run), but who likes rebooting?

> 
> My cygcheck.out is attached.

It would be nice if you could fix your mailer to send attachments
as plain text, and not application/octet-stream.

--
Eric Blake



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