From owner-freebsd-current@freebsd.org Tue Apr 19 14:45:25 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06F77B147E4 for ; Tue, 19 Apr 2016 14:45:25 +0000 (UTC) (envelope-from lidl@pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.pix.net", Issuer "Pix.Com Technologies, LLC CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CC1681499 for ; Tue, 19 Apr 2016 14:45:24 +0000 (UTC) (envelope-from lidl@pix.net) Received: from torb.pix.net (torb.pix.net [192.168.16.32]) (authenticated bits=0) by hydra.pix.net (8.15.2/8.15.2) with ESMTPA id u3JEjNOg074554; Tue, 19 Apr 2016 10:45:23 -0400 (EDT) (envelope-from lidl@pix.net) To: FreeBSD-Current From: Kurt Lidl Subject: issue with /etc/rc.d/mountd script Message-ID: <57164483.3040408@pix.net> Date: Tue, 19 Apr 2016 10:45:23 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 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: Tue, 19 Apr 2016 14:45:25 -0000 Greetings all. I saw something the other day on a machine running 10/stable (but the same code exists in -current), when it was rebooting. The machine acts as a NFS fileserver (to support diskless booting of a few test machines). It only has ZFS filesystems, and only has filesystems that are exported via ZFS properties. So, it has /etc/zfs/exports, but no /etc/exports. When mountd is started up, it emits a error, because the required_files is set to /etc/exports. I think the correct thing is to either remove the required_files setting, or build it from /etc/exports and/or /etc/zfs/exports and only fail if neither of those files exists. (Yes, I could just create an empty /etc/exports file, but that's kinda lame.) -Kurt