X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: sourceware.org
Received-SPF: pass (google.com: domain of fesevur AT gmail DOT com designates 10.52.18.211 as permitted sender) client-ip=10.52.18.211;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of fesevur AT gmail DOT com designates 10.52.18.211 as permitted sender) smtp.mail=fesevur AT gmail DOT com; dkim=pass header.i=fesevur AT gmail DOT com
MIME-Version: 1.0
In-Reply-To: <20120220155801.GC27701@calimero.vinschen.de>
References: <CAKf2h5Qkdu4b1A9dpAsFDHxX-xx-emcKJH+erDD2PdtOjLv80A AT mail DOT gmail DOT com> <20120220155801 DOT GC27701 AT calimero DOT vinschen DOT de>
From: Frank Fesevur <ffes AT users DOT sourceforge DOT net>
Date: Tue, 21 Feb 2012 09:32:01 +0100
Message-ID: <CAKf2h5TyjwocX4i_4bzc4wNYEp8JVGdF-kSY1W6S8FG8GNTwSQ@mail.gmail.com>
Subject: Re: cygrunsrv doesn't stop service during reboot
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q1L8Wpxq022271

2012/2/20 Corinna Vinschen:
> Did you check your log?  Do you see any of these messages?  If not,
> I assume that the shutdown kills the service process so fast that it
> has no chance for the cleanup.  Which is kind of weird in case of
> preshutdown, given that you're supposed to have 3 minutes, at least
> by default...

I check the System log and found this error-line:
The CYGWIN rsyncd service did not shut down properly after receiving a
preshutdown control.

> Interesting.  Given that 2003 doesn't support the control message
> SERVICE_CONTROL_PRESHUTDOWN, it's kind of strange that it works on 2003
> but not on 2008R2.  Did you try to reinstall your rsyncd service without
> the -O option, so that the service acts on the SERVICE_CONTROL_SHUTDOWN
> message instead?

Given the error above, I will try to install the service without the
-O. Should I replace it with a -o or is that default behavior? The
cygrunsrv --help is a bit confusing to me.

Another thing that I thought of was that maybe the -f of the shutdown
command is affecting the process. I will try to test that. But since
this is a production server, I have to wait for the evening to be able
to reboot that server.

Regards,
Frank

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple