Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 11 Oct 2004 00:06:41 -0400 From: Christopher Faylor To: cygwin-xfree AT cygwin DOT com Cc: cygwin AT cygwin DOT com Subject: Re: cygwin/x symantec antivirus conflict (fixed in snapshot?) Message-ID: <20041011040641.GD5016@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin-xfree AT cygwin DOT com, cygwin AT cygwin DOT com References: <4164ABA6 DOT 20205 AT gladstonefamily DOT net> <20041007034237 DOT GE6359 AT trixie DOT casa DOT cgf DOT cx> <41693BD6 DOT 4060304 AT gladstonefamily DOT net> <20041011024427 DOT GC5016 AT trixie DOT casa DOT cgf DOT cx> <4169FEEC DOT 3060607 AT gladstonefamily DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4169FEEC.3060607@gladstonefamily.net> User-Agent: Mutt/1.4.1i Note-from-DJ: This may be spam On Sun, Oct 10, 2004 at 11:33:00PM -0400, Philip Gladstone wrote: >Christopher Faylor wrote: >>Ok. I've changed the algorithm in select. It only opens a DGRAM >>socket now, one time per thread. It uses this to terminate the socket >>thread, if necessary. This socket is never closed until the thread >>terminates. >> >>It sounds like this would more or less fix the problem that you're >>seeing. Would you mind trying a new snapshot? >> >>http://cygwin.com/snapshots/ > >This fixes it for me! Thanks immensely. That's good news! Thanks for the fast feedback. I've cc'ed the cygwin mailing list since this has been a long standing problem. For those who haven't been following along at home, it looks like a change I just made to select() may solve the dreaded "slows down to a crawl with Symantec AntiVirus" problem. This may also improve the performance of things that use sockets slightly. So, I'd appreciate reports on the latest snapshot. Does it fix any problems? Cause any problems? No change? In this one case, I'd like to hear "me toos" since the change was to a fundamental part of cygwin and it is in socket code, which has proved to be problematic. So, I'd like to know if things still work on Windows 9x and all flavors of NT. http://cygwin.com/snapshots/ "Things" would be, openssh, telnet, ftp, rsync, etc. Anything which uses sockets or communicates via TCP/IP. I've reset the reply-to for this message to the cygwin mailing list, so if there is further Cygwin/X discussion necessary, please make sure that it goes to the cygwin-xfree mailing list. cgf -- 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/