From: Ian Kent <raven@themaw.net>
To: "Cyril B." <cbay@excellency.fr>
Cc: "autofs@vger.kernel.org" <autofs@vger.kernel.org>
Subject: Re: [PATCH] Add a --mode option to chmod the mount point of the maps
Date: Mon, 14 Sep 2015 10:31:22 +0800 [thread overview]
Message-ID: <1442197882.3030.33.camel@themaw.net> (raw)
In-Reply-To: <55F58085.4090509@excellency.fr>
On Sun, 2015-09-13 at 15:56 +0200, Cyril B. wrote:
> Hello,
>
> It looks like the mount point of the maps have fixed permissions, 755. I
> need to have different permissions: in my use case, I want /home (which
> is handled by autofs) to be set to 751.
Why is this needed?
>
> The initial permissions of /home are overwritten when autofs is started,
> so changing those doesn't help.
They aren't overwritten.
The permissions are those of the autofs mount that is mounted
over /home.
>
> I can change the permissions of /home after autofs has started, but it's
> really not convenient: there's no easy way to do that automatically with
> either sysvinit or systemd.
I still don't understand why this is needed.
For indirect mounts no-one can copy things into the autofs mount and the
permissions of mounts on mount points will be the same as those of the
mounted file system when they are done.
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next prev parent reply other threads:[~2015-09-14 2:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 13:56 [PATCH] Add a --mode option to chmod the mount point of the maps Cyril B.
2015-09-14 2:31 ` Ian Kent [this message]
2015-09-14 8:42 ` Cyril B.
2015-09-14 9:20 ` Frank Thommen
2015-09-14 9:29 ` Cyril B.
2015-09-14 9:52 ` Ian Kent
2015-09-14 9:45 ` Ian Kent
2015-09-14 10:12 ` Cyril B.
2015-09-14 10:38 ` Ian Kent
2015-09-14 3:05 ` Ian Kent
2015-09-14 3:23 ` Ian Kent
2015-09-14 11:31 ` Cyril B.
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=1442197882.3030.33.camel@themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=cbay@excellency.fr \
/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.