From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "Peter Åstrand" <astrand@cendio.se>, nfs@lists.sourceforge.net
Subject: Re: [patch] provide non-standard getgrouplist() in libnfsidmap when need be
Date: Mon, 26 Mar 2007 12:09:09 -0400 [thread overview]
Message-ID: <20070326160909.GD26422@fieldses.org> (raw)
In-Reply-To: <1174924003.6838.17.camel@heimdal.trondhjem.org>
On Mon, Mar 26, 2007 at 11:46:43AM -0400, Trond Myklebust wrote:
> We're not after the full list of user groups or the group entries.
> libnfsidmap exists purely in order to map a single gid into a group name
> or vice versa and then stuff the result into a kernel cache.
Not currently true, because we're also using libnfsidmap to do the krb
principal -> (uid, gid's) mapping--my mistake.
We should split that code out from libnfsidmap and stick it back into
rpc.svcgssd where it came from.
--b.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-26 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 7:29 [patch] provide non-standard getgrouplist() in libnfsidmap when need be Mike Frysinger
2007-03-26 13:22 ` Trond Myklebust
2007-03-26 14:32 ` Peter Åstrand
2007-03-26 15:46 ` Trond Myklebust
2007-03-26 16:09 ` J. Bruce Fields [this message]
2007-03-26 17:40 ` Mike Frysinger
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=20070326160909.GD26422@fieldses.org \
--to=bfields@fieldses.org \
--cc=astrand@cendio.se \
--cc=nfs@lists.sourceforge.net \
--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