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: Fri, 28 Feb 2003 19:36:38 +0000 From: "Steven O'Brien" To: cygwin AT cygwin DOT com Subject: AF_UNIX in current CVS Message-Id: <20030228193638.50d88598.steven.obrien2@ntlworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 28 Feb 2003 19:03:48 +0100, Corinna Vinschen wrote: > On Fri, Feb 28, 2003 at 01:34:04PM +0000, Steven O'Brien wrote: > > By the way, the current CVS has a problem with unix sockets - they > > are verrrry slow - like several minutes to get a simple message > > through in some cases. > > Simple testcase[tm]? I noticed this as a side-effect of trying to solve the dlopen()/fork() problem on winme; so I don't have a testcase as such. I am trying to get the Gnome desktop to run on win me (it is working very well now on win 2k). As a simplified variation on what I saw, try: $ XWin :0 & $ xclock -display :0 The clock does not appear, at least I gave up waiting after 7 minutes; control-c to get the prompt back. But if you try: $ xclock -display localhost:0 then the clock appears immediately. The difference is that :0 uses a AF_LOCAL socket, while localhost:0 uses a AF_INET socket. Hence my assumption that unix doamin sockets have a problem. This was all with my own build of cygwin1.dll done from a source tree updated at around 11:00 GMT this morning. Of course, it could be my build that is at fault, so if you do not see this problem, then thats fair enough. The last snapshot, 25Feb02, does not have this problem. Regards, Steven -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/