From owner-freebsd-stable@FreeBSD.ORG Fri Jan 7 02:19:07 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 792D4106564A for ; Fri, 7 Jan 2011 02:19:07 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5017F8FC08 for ; Fri, 7 Jan 2011 02:19:07 +0000 (UTC) Received: by pwi10 with SMTP id 10so2698191pwi.13 for ; Thu, 06 Jan 2011 18:19:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=29+PCrBLQOcijpQ6fwztlHml7Psz8zjbrNkeDwYY7lA=; b=YWtNcL/c7caPHA0vw925d9NW4Duj+04LvrZfQzOQikjqkS2J2An5uRQKaiABwX4wZ7 zTZ+NGrsUqvkolzlbhTnRLTsRc3ZwIkp1O0HmTjD4I8MdvS5TvGtdejqVn+E5Av2eKoQ yfRiz5XV7Ay4cjIzyZjVc3KLMWjpcy7xIRuwY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=WLFIT7bI0/VBbagB0/xCAGomU/FA2WlQ7NiF2PeKu2XBPc6KSgru1qVufkmQx3q007 MU6T7sUkn07GVrsxymJzayzJPYpM07l7K82N4nvnQqjezn2rMNHJ2Xtx2HGyGRI8bn8w 7GD8THAg49WbPMjfdheZcaaqhHncYNJmlOues= MIME-Version: 1.0 Received: by 10.142.142.8 with SMTP id p8mr1335046wfd.2.1294366746795; Thu, 06 Jan 2011 18:19:06 -0800 (PST) Received: by 10.142.218.3 with HTTP; Thu, 6 Jan 2011 18:19:06 -0800 (PST) In-Reply-To: <4D2663AE.2080805@FreeBSD.org> References: <4D2663AE.2080805@FreeBSD.org> Date: Thu, 6 Jan 2011 21:19:06 -0500 Message-ID: From: grarpamp To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: NFS - DNS fail stops boot in mountlate X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2011 02:19:07 -0000 So what was unclear? mount_nfs emits a nonzero exit status upon failing to look up an FQDN causing mountlate to trigger a dump to shell on boot during rc processing. That's a *showstopper*. The right thing to do is to hack mount_nfs to punt to background mounting in this case with an appropriate exit status. Personally I'd distinguish mount_nfs exit codes between: 0 - mounted 1 - backgrounded, for any reason 2 - none of the above and adjust the rc's to deal with it accordingly. Words are subject to interpretation and take time. Though perhaps masked by brevity, I believe all the above elements were in the prior concise post. Thanks everybody :)