From owner-freebsd-rc@FreeBSD.ORG Thu Nov 1 20:13:25 2012 Return-Path: Delivered-To: freebsd-rc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B8CBF297; Thu, 1 Nov 2012 20:13:25 +0000 (UTC) (envelope-from crees@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id A0A438FC14; Thu, 1 Nov 2012 20:13:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qA1KDPHZ003880; Thu, 1 Nov 2012 20:13:25 GMT (envelope-from crees@freefall.freebsd.org) Received: (from crees@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA1KDPIu003873; Thu, 1 Nov 2012 20:13:25 GMT (envelope-from crees) Date: Thu, 1 Nov 2012 20:13:25 GMT Message-Id: <201211012013.qA1KDPIu003873@freefall.freebsd.org> To: j.keil@gmx.de, crees@FreeBSD.org, freebsd-rc@FreeBSD.org From: crees@FreeBSD.org Subject: Re: conf/137629: [rc.d] background_dhclient rc.conf option causing double nfs mounts X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list 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: Thu, 01 Nov 2012 20:13:25 -0000 Synopsis: [rc.d] background_dhclient rc.conf option causing double nfs mounts State-Changed-From-To: closed->analyzed State-Changed-By: crees State-Changed-When: Thu Nov 1 20:10:09 UTC 2012 State-Changed-Why: However, this is actually a bug. rc.d/mountlate uses mount -a -d -l to find the filesystems to mount, which assumes that all previous mounts were successful. However, if an NFS mount is still awaited, it is included in that list. I think we'll need a mountlateremote script at first sight, but it could be simpler. http://www.freebsd.org/cgi/query-pr.cgi?pr=137629