From owner-freebsd-current  Sat Jul 18 13:08:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA21703
          for freebsd-current-outgoing; Sat, 18 Jul 1998 13:08:29 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21698
          for <current@freebsd.org>; Sat, 18 Jul 1998 13:08:28 -0700 (PDT)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id NAA15940;
	Sat, 18 Jul 1998 13:03:46 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd015938; Sat Jul 18 20:03:43 1998
Date: Sat, 18 Jul 1998 13:03:37 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
To: Bill Fenner <fenner@parc.xerox.com>
cc: current@FreeBSD.ORG
Subject: Re: State of current... 
In-Reply-To: <199807181852.LAA12992@mango.parc.xerox.com>
Message-ID: <Pine.BSF.3.95.980718130150.17992B-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

bill, I saw mail that said that the problem went away if DISPLAY was
specified with localhost:0.0 instead of :0.0

I BELIEVE that this indicates that what was broken was unix domain
sockets. (but I may  be wrong)


julian

On Sat, 18 Jul 1998, Bill Fenner wrote:

> I backed out the fix.  Does anyone have a test case that would
> reliably fail, so that I can try to figure out exactly what was
> going on?  My testing didn't unveil any problems.
> 
> Thanks,
>   Bill
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message