From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5956 invoked by alias); 17 Feb 2012 18:56:18 -0000 Received: (qmail 5946 invoked by uid 22791); 17 Feb 2012 18:56:16 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from smtpout.karoo.kcom.com (HELO smtpout.karoo.kcom.com) (212.50.160.34) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 17 Feb 2012 18:56:01 +0000 Received: from 213-152-38-55.dsl.eclipse.net.uk (HELO [192.168.1.105]) ([213.152.38.55]) by smtpout.karoo.kcom.com with ESMTP; 17 Feb 2012 18:55:58 +0000 Message-ID: <4F3EA2CF.7040701@dronecode.org.uk> Date: Fri, 17 Feb 2012 18:56:00 -0000 From: Jon TURNEY Reply-To: cygwin-xfree User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com CC: jeffrey.l.bonggren@boeing.ksc.nasa.gov Subject: Re: XWin.exe: _XSERVTransSocketUNIXAccept: accept() failed References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2012-02/txt/msg00037.txt.bz2 On 15/02/2012 16:39, Bonggren, Jeffrey L wrote: > I have recently noticed that XWin.exe is spinning and maxing out a CPU > core. I checked the log and saw that it is spamming it with > "_XSERVTransSocketUNIXAccept: accept() failed" messages at a rate of about > one per millisecond. This is generating a very large log file! Thanks for reporting this. This seems to be related in some way to how you start the X server. Starting it using startxwin.exe (the recommended method), I don't observe this problem, but using your startxwin.bat, I can reproduce the problem. The obvious difference here between these two cases is that we don't have a cygwin process as our immediate ancestor when started from a batch file, but how that could make a difference is a bit mysterious. This seems to be some sort of regression introduced with the cygwin 1.7.10 DLL, downgrading to 1.7.9 doesn't show the problem (although that is problematic as base-files now depends on tzset introduced in 1.7.10) > X seems to be behaving normally in spite of this. I typically run only > xterm and nedit (many instances) locally. > > I have verified that the Windows firewall has a blanket allow rule for > XWin.exe. > > I can't place the exact update that caused this problem, but I believe it > was not having this issue in December 2011. I am never more than a week > behind on updating cygwin. I tried falling back to the previous 1.11.4-2 > version of xorg-server, but it failed to start. Perhaps a version conflict > with some of the other updated packages? As the announce mail says, you need to upgrade xorg-server and libGL1 at the same time. If you downgrade xorg-server, you need to also downgrade libGL1. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/