Date: Wed, 23 Oct 1996 15:45:23 +0800 From: Peter Wemm <peter@spinner.DIALix.COM> To: Heikki Suonsivu <hsu@clinet.fi> Cc: Poul-Henning Kamp <phk@critter.tfs.com>, "Marc G. Fournier" <scrappy@freefall.freebsd.org>, freebsd-bugs@freefall.freebsd.org Subject: Re: bin/926 Message-ID: <199610230745.PAA21759@spinner.DIALix.COM> In-Reply-To: Your message of "Wed, 23 Oct 1996 09:48:53 %2B0300." <199610230648.JAA19608@katiska.clinet.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
Heikki Suonsivu wrote: > > It is ancient wisdom that you mount soft+background in that scenario, > > or wait forever after a power-failure :-) > > Starting mountd before mounting nfs disks corrects this problem and as far > as I know does not have any disadvantages. > > bg mounts won't help, as daemons started in /etc/rc.local might need the > disks (apache, for example, fails to start if it cannot find log files to > write to, or document root is missing). It is possible to kludge around > this but it would be better to fix it, particularly when it is this easy > and does not effect anyone who is not doing cross-mounting (other than nfs > comes up slightly faster after a crash/reboot, which is a plus). Well, unless there's dissent in the ranks, I'll change it to do this. I'd like cross mounting to work reliably myself.. :-) After all, mountd is in /sbin. Hmm, no wait. Doesn't mountd need to do gethostbyname when parsing the /etc/exports file? If so, then it cannot come before named or other name services.... Unless all the hosts in /etc/exports are listed in /etc/hosts, or /etc/resolv.conf points to another machine that is currently up.. Hmm.... Say, that reminds me... This happened in a spectacular way at one of the local universities while I was studying.. They managed to get about 10 or 15 SGI's (way back at IRIX 3.something) deadlocked on cross mounting for quite some time.. Cheers, -Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610230745.PAA21759>