From owner-freebsd-sysinstall@FreeBSD.ORG Mon Dec 31 17:42:37 2012 Return-Path: Delivered-To: freebsd-sysinstall@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1354210D; Mon, 31 Dec 2012 17:42:37 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id C6D8D8FC12; Mon, 31 Dec 2012 17:42:36 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa06.fnfis.com (8.14.5/8.14.5) with ESMTP id qBVHgTgI027597 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 31 Dec 2012 11:42:30 -0600 Received: from [10.0.0.102] (10.14.152.61) by smtp.fisglobal.com (10.132.206.15) with Microsoft SMTP Server (TLS) id 14.2.309.2; Mon, 31 Dec 2012 11:42:29 -0600 Subject: Re: bin/172846: bsdinstall - setting hostname MIME-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset="windows-1252" From: Devin Teske In-Reply-To: <50E1A032.6090901@freebsd.org> Date: Mon, 31 Dec 2012 09:42:27 -0800 Content-Transfer-Encoding: quoted-printable Message-ID: References: <201212311410.qBVEA1o6092589@freefall.freebsd.org> <50E1A032.6090901@freebsd.org> To: Nathan Whitehorn X-Mailer: Apple Mail (2.1283) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327, 1.0.431, 0.0.0000 definitions=2012-12-31_04:2012-12-31,2012-12-31,1970-01-01 signatures=0 Cc: J B , freebsd-sysinstall@FreeBSD.org X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Dec 2012 17:42:37 -0000 sysinstall (and as the PR points out, xauth) used/uses gethostbyname(3) whi= ch could hang if DNS wasn't configured or was configured incorrectly. That'= s the nature of why sysinstall automatically populates hosts(5) with an ent= ry for the current hostname. I've been thinking a lot about whether this is still needed today. Most programs have switched away from gethostbyname(3) and are instead usin= g getaddrinfo(3) and/or getnameinfo(3), but I imagine that since they are f= rom the same family of functions, the replacements to gethostbyname(3) woul= d hang similarly on un/misconfigured DNS. My thinking is that=85 1. Like Nathan, I never configure our systems this way, but that's because = we always have working DNS and if a hang occurs, we know why 2. I believe that maintaining a hosts(5) entry for the local machine name c= ouldn't hurt (but only help those that may not fully grok why their system = is hanging ala illusive typo in resolv.conf etc.). --=20 Devin On Dec 31, 2012, at 6:24 AM, Nathan Whitehorn wrote: > On 12/31/12 09:10, J B wrote: >> The following reply was made to PR bin/172846; it has been noted by GNAT= S. >>=20 >> From: J B >> To: FreeBSD-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org >> Cc:=20=20 >> Subject: Re: bin/172846: bsdinstall - setting hostname >> Date: Mon, 31 Dec 2012 15:02:06 +0100 >>=20 >> Related problem: >> misc/174859: Installation: /etc/hosts file >> jb >> _______________________________________________ >> freebsd-sysinstall@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall >> To unsubscribe, send any mail to "freebsd-sysinstall-unsubscribe@freebsd= .org" >=20 > Is this something it actually makes sense to do? I personally would > never configure my systems this way -- having it done automatically > seems a mistake to me. > -Nathan > _______________________________________________ > freebsd-sysinstall@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall > To unsubscribe, send any mail to "freebsd-sysinstall-unsubscribe@freebsd.= org" _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.