From: Steve Dickson <SteveD@redhat.com>
To: Luk Claes <luk@debian.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsidmap: add default id_resolver.conf
Date: Tue, 28 May 2013 14:43:03 -0400 [thread overview]
Message-ID: <51A4FAB7.5040901@RedHat.com> (raw)
In-Reply-To: <1368468223-21982-1-git-send-email-luk@debian.org>
On 13/05/13 14:03, Luk Claes wrote:
> Ship default id_resolver.conf to put into /etc/request-key.d so
> it is impossible to forget to add the file while upgrading.
Committed even though there was no Signed-off-by line... :-(
steved.
> ---
> utils/nfsidmap/id_resolver.conf | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 utils/nfsidmap/id_resolver.conf
>
> diff --git a/utils/nfsidmap/id_resolver.conf b/utils/nfsidmap/id_resolver.conf
> new file mode 100644
> index 0000000..2c156c6
> --- /dev/null
> +++ b/utils/nfsidmap/id_resolver.conf
> @@ -0,0 +1 @@
> +create id_resolver * * /usr/sbin/nfsidmap -t 600 %k %d
>
prev parent reply other threads:[~2013-05-28 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 18:03 [PATCH] nfsidmap: add default id_resolver.conf Luk Claes
2013-05-28 18:43 ` Steve Dickson [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=51A4FAB7.5040901@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=luk@debian.org \
/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;
as well as URLs for NNTP newsgroup(s).