On Fri, 28 Feb 2003 19:36:38 +0000, Steven O'Brien wrote: > $ 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.
(that should be 25Feb03 of course) The new snapshot, 28 Feb 03 DOES 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/