From: Paul Clements <paul.clements@steeleye.com>
To: mehta kiran <kiranmehta1981@yahoo.com>
Cc: James Pearson <james-p@moving-picture.com>, nfs@lists.sourceforge.net
Subject: Re: file :"/var/lib/nfs/rmtab"
Date: Thu, 03 Feb 2005 11:04:46 -0500 [thread overview]
Message-ID: <42024B9E.1010102@steeleye.com> (raw)
In-Reply-To: <20050203113820.811.qmail@web51601.mail.yahoo.com>
mehta kiran wrote:
> Isn't handle supplied by client
> enough to verify clients access to
> filesystem.?
Yes, it should be. That's why in 2.6, the rmtab file is no longer relied
upon. Instead, there is a special filesystem, /proc/fs/nfsd, that allows
the kernel to communicate with mountd in order to authenticate
unrecognized clients automatically.
--
Paul
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-02-03 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 6:08 file :"/var/lib/nfs/rmtab" mehta kiran
2005-02-03 11:29 ` James Pearson
2005-02-03 11:38 ` mehta kiran
2005-02-03 16:04 ` Paul Clements [this message]
2005-02-04 4:52 ` mehta kiran
2005-02-04 5:01 ` mehta kiran
2005-02-04 10:04 ` James Pearson
2005-02-04 10:55 ` mehta kiran
2005-02-04 12:58 ` James Pearson
2005-02-04 13:22 ` mehta kiran
2005-02-04 14:57 ` James Pearson
2005-02-04 15:49 ` mehta kiran
2005-02-04 15:49 ` mehta kiran
2005-02-04 14:07 ` mehta kiran
2005-02-03 11:38 ` mehta kiran
2005-02-03 11:42 ` mehta kiran
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=42024B9E.1010102@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=james-p@moving-picture.com \
--cc=kiranmehta1981@yahoo.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.