From owner-freebsd-questions@FreeBSD.ORG Tue Oct 11 18:58:31 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 AA99016A41F for ; Tue, 11 Oct 2005 18:58:31 +0000 (GMT) (envelope-from dmarshall@gmail.com) Received: from qproxy.gmail.com (qproxy.gmail.com [72.14.204.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 377C743D48 for ; Tue, 11 Oct 2005 18:58:29 +0000 (GMT) (envelope-from dmarshall@gmail.com) Received: by qproxy.gmail.com with SMTP id a39so1427842qbd for ; Tue, 11 Oct 2005 11:58:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TWtEtJgFyAxydLN/AWUqauP3r086+eh/8AU5tW4tGpX6fT2KacSYqt1cpLM8On1mLeSCwHwBGvorYPQ9GzWEcZq38FQemHl9erc/9mStB+pE4QLxUKDOWBLczn84NQblBytOTUaOlv2tRAozJqzrlPDrZ5CCBpon48KSApfx6LY= Received: by 10.65.138.2 with SMTP id q2mr3485165qbn; Tue, 11 Oct 2005 11:58:26 -0700 (PDT) Received: by 10.65.97.18 with HTTP; Tue, 11 Oct 2005 11:58:26 -0700 (PDT) Message-ID: <53f158630510111158q413667e2u678c290a9b58db5f@mail.gmail.com> Date: Tue, 11 Oct 2005 11:58:26 -0700 From: David Marshall To: Erik Norgaard In-Reply-To: <434B7CBE.3000001@locolomo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <53f158630510110141k50281f15o23fa83e70dbb3036@mail.gmail.com> <434B7CBE.3000001@locolomo.org> Cc: freebsd-questions@freebsd.org Subject: Re: How to Mount NFS Automatically After Boot-Time? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Oct 2005 18:58:31 -0000 Thanks for the great advice! I wasn't able to fiddle with the order of mountcritremote to my satisfaction without creating a circular ordering, so I wound up putting the mount commands I wanted run late in /etc/rc.local, then I fiddled with the load order of /etc/rc.d/local. On 10/11/05, Erik Norgaard wrote: > David Marshall wrote: > > We have several servers that mount from an NFS server for a lot of > > reading and writing. We typically have this mount listed in > > /etc/fstab. > > > > If one of these servers reboots when the NFS server is offline, it > > hangs in single-user mode until the NFS server comes back online. > > > > We have tried usiing amd(8), but the sorts of traffic we have been > > generating has been just a little too much for amd to handle. > > Occasionally it will become overwhelmed and will not work properly > > until it (amd) is restarted. So, it is back to a straight NFS mount. > > > > How can we cause this NFS mount to be made after the system has > > reached multi-user so that we can log in and perhaps mount from > > another server? (The servers are in a colo, so it's not easy to gain > > physical access to the console to operate the machine in single-user.) > > > > I've played with putting a mount command into /etc/rc.local, but I > > don't know whether that would make us equally susceptible to a server > > outage. > > If you look in /etc/rc.d/ there are two scripts: mountcritlocal and > mountcritremote - the last one mounts nfs mounts if present in fstab. > > In the beginning of the file you will find the lines: > > # PROVIDE: mountcritremote > # REQUIRE: NETWORKING root mountcritlocal cleanvar > # KEYWORD: nojail > > These are comments for /bin/sh but the affect the order of execution. > The scripts in /etc/rc.d are executed in the order sorted by > /sbin/rcorder(8) > > So, you can postpone the nfs mounts till later by changing the REQUIRE > line. Note that some scripts may have "mountcritremote" in their REQUIRE > line. > > Hope this helps, > > Erik > -- > Ph: +34.666334818 web: www.locolomo.org > S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt > Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 > Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 >