From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 3 19:34:28 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7326F16A41F for ; Sat, 3 Sep 2005 19:34:28 +0000 (GMT) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0029143D45 for ; Sat, 3 Sep 2005 19:34:27 +0000 (GMT) (envelope-from ml@t-b-o-h.net) Received: from himinbjorg.tucs-beachin-obx-house.com (ool-44c511d8.dyn.optonline.net [68.197.17.216]) (authenticated bits=128) by vjofn.tucs-beachin-obx-house.com (8.12.9/8.12.9) with ESMTP id j83JY58p005297; Sat, 3 Sep 2005 15:34:06 -0400 (EDT) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1]) by himinbjorg.tucs-beachin-obx-house.com (8.13.3/8.12.10) with ESMTP id j83JXt0B050464; Sat, 3 Sep 2005 15:33:59 -0400 (EDT) (envelope-from ml@t-b-o-h.net) Received: (from tbohml@localhost) by himinbjorg.tucs-beachin-obx-house.com (8.13.3/8.13.1/Submit) id j83JXtfZ050463; Sat, 3 Sep 2005 15:33:55 -0400 (EDT) (envelope-from tbohml) From: Tuc at T-B-O-H Message-Id: <200509031933.j83JXtfZ050463@himinbjorg.tucs-beachin-obx-house.com> To: stas@310.ru (Stanislav Sedov) Date: Sat, 3 Sep 2005 15:33:54 -0400 (EDT) In-Reply-To: <20050903171621.GA3927@core.310.ru> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: rc sequencing issue / mountcritremote X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2005 19:34:28 -0000 > > On Sat, Sep 03, 2005 at 12:20:41PM -0400, Tuc at T-B-O-H wrote: > > > The problem I'm having is that when it attempts to remotely > > mount the NFS filesystem I need, there are no support programs > > running, namely (I THINK) : > > > > /etc/rc.d/rpcbind > > /etc/rc.d/nfsclient > > /etc/rc.d/mountd > > /etc/rc.d/nfsd > > /etc/rc.d/nfslocking > > This is wrong, you don't need anything to mount remote NFS filesystems. > nfsclient only sets some useful sysctls. > See handbook for details. > nfsclient not only does sysctls, but also runs rpc.umntall via a dependency. I would still think the best time to do this is before the remote filesystem is mounted. Since there are other items that need rpcbind, it should be started first, and again I think before the filesystem. In checking more, the mountd isn't needed. The nfsd seems to take into account nfsserver, rpcbind, mountd and a sysctl. However, the biggest one after rpcbind I would think is nfslocking. It runs rpc.statd and rpc.lockd. I've run into ALOT of problems with things if locking isn't running. So isn't this also necessary before the mount? I know I use the remote filesystem very soon after its mounted, so it would need to be running very early on. So, even with the others not running, wouldn't I need rpcbind and nfslocking done just before remotemountcrit? One other thing I didn't touch too much on, is what about the DNS resolution for the remote mount? named isn't running until much later, so it hangs.... Isn't that something that should be running so the resolution can happen? Thanks, Tuc