On 1/27/07, Hans-Joachim Widmaier <[EMAIL PROTECTED]> wrote:
> Randy McMurchy wrote:
> >
> > I meant to take care of this many, many months ago but apparently it
> > fell through the cracks. I noticed in a recently built system that
> > after installing the NFS server and starting the daemons, at shutdown
> > time the NFS Server would not stop as it should. It would time out for
> > a *long* time, then finally come back with an error saying it couldn't
> > stop the daemon, then continue to shut down.
>
> This is bugging me since months. I always thought that to be a problem
> with nfsd ... (this was on my little older box with
> blfs-bootscripts-20060624).
>
> > I noticed that it was using "killproc nfsd" as the command to shut
> > down the nfsd daemons. However, I changed my bootscript to say
> > "killproc [nfsd]" and it worked as it is supposed to. (noticed the
> > square brackets around 'nfsd')
>
> Didn't work for me. So I checked the 20060910 version, which uses ${2}
> to communicate the signal to use, and no longer waiting. BUT: killing
> nfsd has now a [FAIL] at the end. The nfsd _are_ killed, though.
>
> I've checked the nfsd man page and found another method to stop nfsd:
> "/usr/sbin/rpc.nfsd 0". Together with "evaluate_retval" this looks like
> it works reliably (and quick) for me.I don't use nfs, but out of curiosity I checked what the fedora bootscript does. It's roughly the same, using `killproc nfsd'. Of course, I don't know exactly what killproc does on fedora. The one difference I saw is that rpc.mountd is stopped first and then nfsd. This is the opposite of BLFS. You could try that and see what happens. http://cvs.fedora.redhat.com/viewcvs/devel/nfs-utils/nfs.init?view=markup -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
