linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Martin Wege <martin.l.wege@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: export(5) all_squash, only new files squashed, or all uid/gids?
Date: Thu, 7 Mar 2024 14:39:25 +0100 (CET)	[thread overview]
Message-ID: <1001845535.26063.1709818765823.JavaMail.zimbra@desy.de> (raw)
In-Reply-To: <CANH4o6OxmxNXNhbZ6THwPVAtfkbkdYyQUMRGCX_=Ssb1gTUXJg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

Hi Martin,

The option all_squash does not affect files or directories.
It replaces RPC request credentials sent by nfs client with
user nobody:nobody. The newly created files will be owned by
nobody:nobody, if parent directory permission
(and export rules) allow to do so.

Best regards,
   Tigran.



----- Original Message -----
> From: "Martin Wege" <martin.l.wege@gmail.com>
> To: "Linux NFS Mailing List" <linux-nfs@vger.kernel.org>
> Sent: Sunday, 3 March, 2024 14:31:37
> Subject: export(5) all_squash, only new files squashed, or all uid/gids?

> Hello,
> 
> How does the export(5) option all_squash export option work? Does it
> only squash the uid/gid of new files to nobody/nogroup, or will it
> turn the uid/gids of all existing files in the exported tree to
> nobody/nogroup?
> 
> Thanks,
> Martin

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2826 bytes --]

      reply	other threads:[~2024-03-07 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03 13:31 export(5) all_squash, only new files squashed, or all uid/gids? Martin Wege
2024-03-07 13:39 ` Mkrtchyan, Tigran [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=1001845535.26063.1709818765823.JavaMail.zimbra@desy.de \
    --to=tigran.mkrtchyan@desy.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=martin.l.wege@gmail.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 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).