Date: Sat, 18 Jul 1998 17:40:38 -0400 (EDT) From: Brian Feldman <green@zone.baldcom.net> To: Julian Elischer <julian@whistle.com> Cc: Bill Fenner <fenner@parc.xerox.com>, current@FreeBSD.ORG Subject: Re: State of current... Message-ID: <Pine.BSF.3.96.980718173643.5240A-100000@zone.baldcom.net> In-Reply-To: <Pine.BSF.3.95.980718130150.17992B-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, this was the exact problem. The atomic = 1; assignment caused quite a large amount of breakage, mainly with X geometry calls, etc. using localhost:0.0, I.E. using tcp port 6000 for communication rather than the /tmp X11 socket. I am still experiencing intermittent complaints from WindowMaker of the same vein as those reported for other apps, however WindowMaker doesn't seem to crash at all, and seems to be the only program still exhibiting problems. Will investigate more.... Brian Feldman green@zone.baldcom.net On Sat, 18 Jul 1998, Julian Elischer wrote: > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980718173643.5240A-100000>