From: "David Shirley" <dave@cs.curtin.edu.au>
To: "Christian Reis" <kiko@async.com.br>,
"Trond Myklebust" <trond.myklebust@fys.uio.no>
Cc: <NFS@lists.sourceforge.net>
Subject: Re: Re: /var/lib/nfs/sm/ files
Date: Wed, 8 Jan 2003 16:08:42 +0800 [thread overview]
Message-ID: <00ed01c2b6ed$2a9d9530$64070786@synack> (raw)
In-Reply-To: shsn0mcj3x8.fsf@charged.uio.no
Trond,
Will the client automatically remount or fix the mount
once the server comes back up? ie after the server
notifys the client, or does the client still have to restart
nfs?
Cheers
Dave
----- Original Message -----
From: "Trond Myklebust" <trond.myklebust@fys.uio.no>
To: "Christian Reis" <kiko@async.com.br>
Cc: <NFS@lists.sourceforge.net>; <linux-kernel@vger.kernel.org>
Sent: Wednesday, January 08, 2003 12:54 AM
Subject: [NFS] Re: /var/lib/nfs/sm/ files
> >>>>> " " == 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.
>
> Cheers,
> Trond
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
>
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-01-08 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 15:27 /var/lib/nfs/sm/ files Christian Reis
2003-01-07 16:54 ` Trond Myklebust
2003-01-08 8:08 ` David Shirley [this message]
2003-01-08 9:13 ` Trond Myklebust
2003-01-08 11:50 ` Christian Reis
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='00ed01c2b6ed$2a9d9530$64070786@synack' \
--to=dave@cs.curtin.edu.au \
--cc=NFS@lists.sourceforge.net \
--cc=kiko@async.com.br \
--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 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.