X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4A1EC66C.50806@cygwin.com> References: <1de9d39c0905280711r6e9474edi42f19c07905530ef AT mail DOT gmail DOT com> <4A1EC66C DOT 50806 AT cygwin DOT com> Date: Fri, 29 May 2009 12:33:21 +0200 Message-ID: <1de9d39c0905290333k68713ba9i97e8f834f44e4800@mail.gmail.com> Subject: Re: limited connection numbers to X? From: jean-luc malet To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Thu, May 28, 2009 at 7:14 PM, Larry Hall (Cygwin) wrote: > jean-luc malet wrote: >> >> Hi, >> after opening about 15 to 20 connection to X, all further connection >> will end with an error "can't connect to X server" >> since I have lot of vim and xterm opened I must close some to open new >> ones... >> is it a known feature? it happens only on cygwin1.7 > > This is probably better sent to the cygwin-xfree list since it could be a > X thing. > it happened just after upgrading le cygwin.dll do 1.7, before it was working fine, X hasn't been upgraded if I'm correct so it seems more related to cygwin.dll and maybe socket limitation... JLM -- 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/