Date: Sun, 6 Nov 2011 22:07:57 -0500 From: Robert Simmons <rsimmons0@gmail.com> To: freebsd-fs@freebsd.org Subject: Re: rpc.umntall error on boot Message-ID: <CA%2BQLa9AA5fh-kwORjJg_2g03C5z1K8OkNTLxnk0_gdFBzarPGQ@mail.gmail.com> In-Reply-To: <1508064123.1257002.1320626685087.JavaMail.root@erie.cs.uoguelph.ca> References: <CA%2BQLa9AK8jK5E-WXNTDHZfmDf19ZgCNK4BuWVc5Jtr=H2pq-4Q@mail.gmail.com> <1508064123.1257002.1320626685087.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 6, 2011 at 7:44 PM, Rick Macklem <rmacklem@uoguelph.ca> wrote: > What happens is that /etc/rc.d/nfsclient is executed before > /etc/rc.d/mountd. It finds /var/db/mountdtab non-empty and tries to > get a port from rpcbind for mountd. Since mountd isn't running yet, > so it fails. Since telling the server on the same machine to clear > out /var/db/mountdtab for the client is basically meaningless, failing > shouldn't be a problem. Would there be any drawbacks to moving /etc/rc.d/nfsclient to later in the process so that mountd is already running? Rob
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9AA5fh-kwORjJg_2g03C5z1K8OkNTLxnk0_gdFBzarPGQ>