From owner-freebsd-questions@FreeBSD.ORG Fri Nov 19 15:17:58 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FFB016A4CE for ; Fri, 19 Nov 2004 15:17:58 +0000 (GMT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id F25ED43D2F for ; Fri, 19 Nov 2004 15:17:57 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 96E8AB86A for ; Fri, 19 Nov 2004 09:17:57 -0600 (CST) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03832-09 for ; Fri, 19 Nov 2004 09:17:56 -0600 (CST) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id CB97EB83B for ; Fri, 19 Nov 2004 09:17:56 -0600 (CST) From: Kirk Strauser To: freebsd-questions@freebsd.org Date: Fri, 19 Nov 2004 09:17:47 -0600 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart275222222.mSdNL5fzpe"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411190917.51162.kirk@strauser.com> X-Virus-Scanned: by amavisd-new at honeypot.net Subject: /etc/rc.d/mountcritremote and nfsserver X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 15:17:58 -0000 --nextPart275222222.mSdNL5fzpe Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline This is a short question, but I'll make it long anyway. Those short on time may want to skip to the last paragraph. I run several servers that each host a few jail environments, and I use NFS as a kind of loopback filesystem to share common directories among them. =46or example, my /etc/fstab is populated with entries like: hostmachine:/usr/ports /var/jail/virtual1/usr/ports = nfs ro 0 0 hostmachine:/usr/ports/distfiles /var/jail/virtual1/usr/ports/distfiles= nfs rw 0 0 Until recently, I've been using the sysutils/jailadmin port (plug: which I wrote ;-) ) to start and stop these jails, and one of its features is that it can automatically mount a jail's filesystems immediately before it starts it and then umount them when the jail is stopped. Consequently, I've always had the `noauto' option in /etc/fstab in all of those NFS entries. A few days ago, though, I decided to try the much-improved rc.d/jail script, and it works well enough now that I'm about ready to orphan jailadmin and concentrate on improving rc.d/jail instead. However, `jail' does not (yet) support the automatic mounting of a jail's filesystems, so I have to let the boot sequence take care of that. If I remove the `noauto' option, then the machines hang at boot in rc.d/mountcritremote, since it runs before rc.d/nfsserver. As someone new to the whole rc.d idea, I have to ask: is it OK to add `nfsserver' to the REQUIRE line in `mountcritremote'? Is there any reason not to? Would this make sense as a patch for FreeBSD in general? =2D-=20 Kirk Strauser --nextPart275222222.mSdNL5fzpe Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iD8DBQBBng6f5sRg+Y0CpvERAjRQAJ0S+MsjXsg8OmMkzhT7NpfDy+a0DgCfdQym YoJNmTK+9l1cLhKWZZbhOuU= =vpS7 -----END PGP SIGNATURE----- --nextPart275222222.mSdNL5fzpe--