From owner-freebsd-current Fri Mar 10 04:46:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA14557 for current-outgoing; Fri, 10 Mar 1995 04:46:55 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA14551 for ; Fri, 10 Mar 1995 04:46:48 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA32339; Fri, 10 Mar 1995 22:41:19 +1000 Date: Fri, 10 Mar 1995 22:41:19 +1000 From: Bruce Evans Message-Id: <199503101241.WAA32339@godzilla.zeta.org.au> To: dfr@render.com, hsu@cs.hut.fi Subject: Re: nfs mounts backgrounded? Cc: freebsd-current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk >> -current now backgrounds NFS mounts in /etc/rc? This breaks up things when >> local is mounted over NFS and local additions /etc/rc.local try to start up >> programs from local (which isn't mounted yet)? Are there any problems with >> not backgrounding the mount? >FreeBSD has always done this and I have always hacked out the background >in /etc/rc. Its never done me any harm. I always hack out the background and move the mount earlier so that /usr can be mounted over NFS. This causes the system to hang if the server isn't up, but that's what I want. Bruce *** /usr/src/etc/rc Sat Jan 28 20:40:13 1995 --- rc Sat Jan 28 20:41:08 1995 *************** *** 92,97 **** --- 92,99 ---- echo 'starting network' . /etc/netstart + mount -a -t nfs + # clean up left-over files rm -f /etc/nologin rm -f /var/spool/lock/* *************** *** 226,233 **** echo -n ' inetd'; inetd echo '.' - - mount -a -t nfs >/dev/null 2>&1 & # XXX shouldn't need background # if [ -x /usr/libexec/xtend ]; then # echo -n ' xtend'; /usr/libexec/xtend --- 228,233 ----