From: Jim Rees <rees@umich.edu>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Orion Poplawski <orion@cora.nwra.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Any way to allow setuid daemon to access krb5 automounted nfs directories?
Date: Wed, 26 Sep 2012 07:45:54 -0400 [thread overview]
Message-ID: <20120926114554.GA7683@umich.edu> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA908FE99CE@SACEXCMBX04-PRD.hq.netapp.com>
Myklebust, Trond wrote:
> -----Original Message-----
> From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-
> owner@vger.kernel.org] On Behalf Of Jim Rees
> Sent: Tuesday, September 25, 2012 1:50 PM
> To: Orion Poplawski
> Cc: linux-nfs@vger.kernel.org
> Subject: Re: Any way to allow setuid daemon to access krb5 automounted
> nfs directories?
>
> But I hope you're not planning to deliver mail over nfs. I think that would be a
> mistake.
What's wrong with that? Delivering and serving up email is a fairly common
use-case for NFS.
Nothing against spamd or NFS in particular. It's just that some mailers
assume the file system is a local disk and are not prepared for the kinds of
failures you can get over a network.
prev parent reply other threads:[~2012-09-26 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 16:44 Any way to allow setuid daemon to access krb5 automounted nfs directories? Orion Poplawski
2012-09-25 17:50 ` Jim Rees
2012-09-25 20:11 ` Orion Poplawski
2012-09-25 20:52 ` Myklebust, Trond
2012-09-26 11:45 ` Jim Rees [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=20120926114554.GA7683@umich.edu \
--to=rees@umich.edu \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=orion@cora.nwra.com \
/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.