X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-Authenticated: #19222419 Message-ID: <48E19F48.1050805@gmx.net> Date: Tue, 30 Sep 2008 05:38:48 +0200 From: Sybille Ebert User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygserver 1.5.25-15 slows down logoff References: <48BEB7F8 DOT 2080908 AT gmx DOT net> <48BF5B9D DOT 1010501 AT gmx DOT net> <20080929164910 DOT GB11053 AT calimero DOT vinschen DOT de> In-Reply-To: <20080929164910.GB11053@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.65 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 >>> I am running cygserver service on Windows 2003 x64 SP2 on dual-core. If >>> the service is running, there is a significant delay during log >>> off/shutdown (approx. 1-2 minutes). If cygserver service is stopped, the >>> logoff takes just 1-2 seconds. >>> >>> I have no other Cygwin services installed, and no Cygwin process started >>> as the logged-on user. >> Here are some more facts about cygserver hanging during logoff: > > Does that problem appear at logoff or at shutdown. or both? Is > cygserver in use by applications in that scenario? There's a chance > that cygserver has worker threads running which are waiting for > interaction with a calling application. It appears when local user logs off and when you shutdown/restart the system. It does NOT appear when remote desktop user logs off, however. I do not think that cygserver has any active worker threads. You can start it afresh, and with no other cygwin processes running, it still hangs. On a side note: manually stopping cygserver is fast, it does not appear to trigger the problem. > >> - the problem is specific to Windows 2003 64-bit, it does not appear in >> Windows XP 32-bit > > There's no special code in Cygwin which would handle logoff/shutdown > scenarios differently on x86 vs. x64 systems, though... I thought so. A few timestamped debug messages would probably be enough to pinpoint the code in which cygserver is spending time... The problem also appears in sshd service, eventhough it does not depend on cygserver. I installed sshd using ssh-host-config and manually stopped cygserver. And even with only sshd running, there was still a long delay at logoff/shutdown! S -- 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/