From owner-freebsd-doc Thu Mar 7 1:19:11 2002 Delivered-To: freebsd-doc@freebsd.org Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id A5EEB37B404 for ; Thu, 7 Mar 2002 01:19:07 -0800 (PST) Received: from pc4-card4-0-cust162.cdf.cable.ntl.com ([80.4.14.162] helo=rhadamanth.private.submonkey.net ident=mailnull) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 16iu3G-0006S2-00 for freebsd-doc@freebsd.org; Thu, 07 Mar 2002 09:19:06 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.35 #1) id 16iu1Y-0001iE-00; Thu, 07 Mar 2002 09:17:20 +0000 Date: Thu, 7 Mar 2002 09:17:20 +0000 From: Ceri To: Giorgos Keramidas Cc: Tom Rhodes , freebsd-doc@freebsd.org Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Message-ID: <20020307091720.GA6465@submonkey.net> Mail-Followup-To: Ceri , Giorgos Keramidas , Tom Rhodes , freebsd-doc@freebsd.org References: <200203052340.g25Ne2R93047@freefall.freebsd.org> <20020306171838.GC11735@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020306171838.GC11735@hades.hell.gr> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Mar 06, 2002 at 07:18:38PM +0200, Giorgos Keramidas wrote: > The patch now seems rather nice. To all of you NFS gurus out there, one > last question, this time a bit technical and on the side of correctness of > the instructions we show in our samples to our poor^Wnewbie users :-) > > > - On the NFS server: > > + On the NFS server: > > > > &prompt.root; portmap > > &prompt.root; nfsd -u -t -n 4 > > &prompt.root; mountd -r > > What happens if portmap is already running? Will starting portmap again, > make sure that the old portmapper dies gracefully? Or should we add proper > killall commands in between those lines for each of the programs started. It just pukes out : {setantae@rhadamanth}-{~} $ su Password: {root@rhadamanth}-{/home/setantae} # ps -ax |grep portmap 112 ?? Is 0:00.00 /usr/sbin/portmap -h 192.168.10.1 {root@rhadamanth}-{/home/setantae} # portmap {root@rhadamanth}-{/home/setantae} # ps -ax |grep portmap 112 ?? Is 0:00.00 /usr/sbin/portmap -h 192.168.10.1 {root@rhadamanth}-{/home/setantae} # grep portmap /var/adm/all.log Mar 7 09:12:45 rhadamanth portmap[6460]: cannot bind udp: Address already in use {root@rhadamanth}-{/home/setantae} # exit > > - On the NFS client: > > + On the NFS client: > > > > &prompt.root; nfsiod -n 4 > > Ditto. Does the administrator of the NFS client machine have to kill > already running nfsiod processes before starting nfsiod again? I only have a -current NFS client, but this is what that does : {root@amam}-{/home/setantae} # ps -ax |grep nfsiod 31 ?? IL 0:00.02 (nfsiod 0) 32 ?? IL 0:00.02 (nfsiod 1) 33 ?? IL 0:00.00 (nfsiod 2) 34 ?? IL 0:00.00 (nfsiod 3) 27559 p0 S+ 0:00.01 grep nfsiod {root@amam}-{/home/setantae} # nfsiod -n 4 {root@amam}-{/home/setantae} # ps -ax | grep nfsiod 31 ?? IL 0:00.02 (nfsiod 0) 32 ?? IL 0:00.02 (nfsiod 1) 33 ?? IL 0:00.00 (nfsiod 2) 34 ?? IL 0:00.00 (nfsiod 3) 27567 p0 RV 0:00.00 grep nfsiod (csh) {root@amam}-{/home/setantae} # grep nfsiod /var/adm/messages Mar 7 09:15:26 amam nfsiod:[27562]: nfssvc: Device not configured Mar 7 09:15:26 amam nfsiod:[27563]: nfssvc: Device not configured Mar 7 09:15:26 amam nfsiod:[27564]: nfssvc: Device not configured Mar 7 09:15:26 amam nfsiod:[27565]: nfssvc: Device not configured {root@amam}-{/home/setantae} # Ceri -- keep a mild groove on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message