From: Christian Reis <kiko@async.com.br>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: /var/lib/nfs/sm/ files
Date: Wed, 8 Jan 2003 09:50:50 -0200 [thread overview]
Message-ID: <20030108095050.C22321@blackjesus.async.com.br> (raw)
In-Reply-To: <shsn0mcj3x8.fsf@charged.uio.no>; from trond.myklebust@fys.uio.no on Tue, Jan 07, 2003 at 05:54:59PM +0100
On Tue, Jan 07, 2003 at 05:54:59PM +0100, Trond Myklebust wrote:
> >>>>> " " == Christian Reis <kiko@async.com.br> writes:
>
> > Hi there,
>
> > Can `anybody' (Neil, Trond?) explain what the entries in
> > /var/lib/nfs/sm/ are for? If they refer to file locks, can we
>
> 'man rpc.statd'. Those files store the IP-addresses of the machines
> being monitored by statd. In case of a crash or a reboot, those files
> tell statd which machines that need to be notified.
Thanks. So my questions are related to what `monitored by statd' means:
- Why don't all the diskless workstations get an entry in that
directory while they are running? Right now I have 5 running, and
only one has an entry there.
- Why do most entries' mtime get updated periodically, but a few of
the entries go stale with time?
- Why do some of the stale entries get left over even after the
workstations have halted (these ones present the nfs hang issue)?
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
next prev parent reply other threads:[~2003-01-08 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 15:27 Christian Reis
2003-01-07 16:54 ` Trond Myklebust
2003-01-08 11:50 ` Christian Reis [this message]
2003-01-08 12:46 ` Trond Myklebust
2003-01-08 17:14 ` Christian Reis
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=20030108095050.C22321@blackjesus.async.com.br \
--to=kiko@async.com.br \
--cc=NFS@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome