From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Matthew Mitchell <matthew@geodev.com>
Cc: trond.myklebust@fys.uio.no, nfs@lists.sourceforge.net
Subject: Re: More about nfsd/lockd hang in 2.4.20+NFS_ALL
Date: 13 Jun 2003 14:21:25 -0700 [thread overview]
Message-ID: <shsk7bpy8q2.fsf@charged.uio.no> (raw)
In-Reply-To: <3EEA006C.2080203@geodev.com>
>>>>> " " == Matthew Mitchell <matthew@geodev.com> writes:
> According to rpcinfo on this server, which is also the client,
> port 32769 is "sgi_fam". What is that? status is 32768.
> Perhaps it's rejecting it with good cause.
fam has nothing to do with NFS. It is a 'file alteration
monitor'. ('man fam')
> Hmm. So the messages from lockd could just be a symptom of the
> problem (nfsd locking up), you think. I first noticed the
> problem when a remote user logged into the server, and the home
> directory (exported by the server) got remounted by the
> automounter on a local path.
If you think that fam is screwing with NFS then kill it. It is hardly
a critical service on most setups.
Cheers,
Trond
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-06-13 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 13:46 More about nfsd/lockd hang in 2.4.20+NFS_ALL Matthew Mitchell
2003-06-13 15:48 ` Trond Myklebust
2003-06-13 16:19 ` Matthew Mitchell
2003-06-13 16:31 ` Trond Myklebust
2003-06-13 16:48 ` Matthew Mitchell
2003-06-13 21:21 ` Trond Myklebust [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=shsk7bpy8q2.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=matthew@geodev.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.