From owner-freebsd-rc@FreeBSD.ORG Tue Dec 27 22:30:19 2005 Return-Path: X-Original-To: freebsd-rc@hub.freebsd.org Delivered-To: freebsd-rc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67E4616A41F for ; Tue, 27 Dec 2005 22:30:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C56F443D64 for ; Tue, 27 Dec 2005 22:30:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBRMUIom065655 for ; Tue, 27 Dec 2005 22:30:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBRMUIYc065653; Tue, 27 Dec 2005 22:30:18 GMT (envelope-from gnats) Date: Tue, 27 Dec 2005 22:30:18 GMT Message-Id: <200512272230.jBRMUIYc065653@freefall.freebsd.org> To: freebsd-rc@FreeBSD.org From: JoaoBR Cc: Subject: Re: conf/90863: [patch] 6.0 boot: name resolution broken for daemon startup X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: JoaoBR List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2005 22:30:19 -0000 The following reply was made to PR conf/90863; it has been noted by GNATS. From: JoaoBR To: bug-followup@freebsd.org, wollman@xyz.csail.mit.edu Cc: Subject: Re: conf/90863: [patch] 6.0 boot: name resolution broken for daemon startup Date: Tue, 27 Dec 2005 20:29:05 -0200 I think that named is not starting first and so I guess the rc start order = is=20 wrong and not that named do not answer queries,=20 I reported similar here: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D86668 also I believe that this touches the same problem that the timeout is too=20 long, see this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/62139 (even if this is apearently to ssh related the problem is the sshd dns reso= lve=20 timeout which is too long) In my opinion the rc order needs to be corrected and the resolv timeout nee= ds=20 to be shorter and a proper error messages on startup would help to understa= nd=20 the problem because hanging on starting sendmail . makes believe the problem is in sendmail configuration Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br