Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: Sat, 1 Mar 2003 08:53:18 +0000
From: "Steven O'Brien" <steven DOT obrien2 AT ntlworld DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: AF_UNIX in current CVS
Message-Id: <20030301085318.7e614632.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: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/