Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!ucsd!ames!sgi!vjs@rhyolite.wpd.sgi.com
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Newsgroups: comp.sys.sgi
Subject: Re: Mountd keeps dying
Message-ID: <52495@sgi.sgi.com>
Date: 2 Mar 90 18:56:58 GMT
References: <9003012042.AA18640@Icarus2.AE.MsState.Edu>
Sender: vjs@rhyolite.wpd.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 30

In article <9003012042.AA18640@Icarus2.AE.MsState.Edu>, larryt@AE.MSSTATE.EDU (Larry Thorne) writes:
> ...
> Anyhow, is this the cause of rpc.mountd dying?  Is there any way to get
> an error message from rpc.mountd before it dies?  How can I tell what's
> causing all this?  Do I need to start more nfsd processes?
> 
> Larry Thorne
> larryt@ae.msstate.edu

What is meant by "dying"?  We run mountd as an inetd deamon, so that
it should live only long enough to service one (or more recently a batch)
of requests.  There have been versions that lived until killed, but
I don't think they were shipped.

If you are seeing dying as in core files, it would be good to communicate
with the Hotline.

If you are seeing dying as in inetd or portmap not answering, that is
another problem the Hotline should hear about.

Nfsd has little to do with mounting.  The `rpcinfo -p` command can be
useful to see if portmap is running and knows that inetd is willing
to start mountd.  The `netstat -a` command can be used to see if
inetd is in fact listening on the port that portmap thinks it is.
Nfsstat can also be useful.


Vernon Schryver
Silicon Graphics
vjs@sgi.com