Date: Thu, 7 Mar 2002 09:17:20 +0000 From: Ceri <setantae@submonkey.net> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: Tom Rhodes <darklogik@pittgoth.com>, freebsd-doc@freebsd.org Subject: Re: docs/35098: [PATCH] Handbook NFS stuff Message-ID: <20020307091720.GA6465@submonkey.net> In-Reply-To: <20020306171838.GC11735@hades.hell.gr> References: <200203052340.g25Ne2R93047@freefall.freebsd.org> <20020306171838.GC11735@hades.hell.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :-)
>
> > - <para>On the NFS server:</para>
> > + <para>On the <acronym>NFS</acronym> server:</para>
> >
> > <screen>&prompt.root; <userinput>portmap</userinput>
> > &prompt.root; <userinput>nfsd -u -t -n 4</userinput>
> > &prompt.root; <userinput>mountd -r</userinput></screen>
>
> 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
> > - <para>On the NFS client:</para>
> > + <para>On the <acronym>NFS</acronym> client:</para>
> >
> > <screen>&prompt.root; <userinput>nfsiod -n 4</userinput></screen>
>
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020307091720.GA6465>