From owner-freebsd-current@FreeBSD.ORG Sun Feb 29 21:05:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11D7816A4D2 for ; Sun, 29 Feb 2004 21:05:17 -0800 (PST) Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 031C643D1F for ; Sun, 29 Feb 2004 21:05:10 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (16df10520b19b7f0782f4cd27d0a04c0@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203])i2155AX0018929; Sun, 29 Feb 2004 21:05:10 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 552DF53410; Sun, 29 Feb 2004 21:05:08 -0800 (PST) Date: Sun, 29 Feb 2004 21:05:08 -0800 From: Kris Kennaway To: Nate Lawson Message-ID: <20040301050507.GA50795@xor.obsecurity.org> References: <20040228152618.C98870@root.org> <1078019158.18071.12.camel@shumai.marcuscom.com> <1078020761.18071.15.camel@shumai.marcuscom.com> <1078032512.20048.7.camel@shumai.marcuscom.com> <1078102552.62463.64.camel@shumai.marcuscom.com> <20040229170401.Q3406@root.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <20040229170401.Q3406@root.org> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: mozilla hanging on gconfd2 startup? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2004 05:05:17 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 29, 2004 at 05:07:42PM -0800, Nate Lawson wrote: > > > So it does appear that the hostname is the issue. However, on a mozi= lla > > > 1.5 and a -current of a few weeks ago, this was not a problem. So wh= at > > > changed? > > > > The gconf "dependency" was most likely added in 1.6. The solution to > > this is to add your local hostname to /etc/hosts (that's the common > > answer to GNOME users encountering this lock in gconfd). If you don't > > want to do that, the pref trick is another valid workaround, but I think > > the hostname thing makes more sense. >=20 > Attempts to add the hostname as 127.0.0.1 and the actual IP resulted in a > hang in the same place. A tcpdump of both lo0 and fxp0 show no more DNS > queries so the hosts entry was definitely being used. A telnet to the > hostname also shows that the lookup succeeds. Since there were no > segments of TCP or UDP, I'm at a loss why it is blocking still. I came into the thread late, but is this related to green's recent commits breaking binary compatibility of the libc DNS resolver? Kris --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAQsSDWry0BWjoQKURAqiTAKDPP4ExsfJhSO/0L1jB4C55dFQOPwCdHIJ6 iO/VnwxPCLqRtWTGWlxFylg= =HK/I -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/--