All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: cbay@excellency.fr
Cc: Frank Thommen <frank.thommen@embl-heidelberg.de>,
	"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 17:52:20 +0800	[thread overview]
Message-ID: <1442224340.3030.70.camel@themaw.net> (raw)
In-Reply-To: <55F69382.2060605@excellency.fr>

On Mon, 2015-09-14 at 11:29 +0200, Cyril B. wrote:
> Frank Thommen wrote:
> > They are not "re"set.  These are the permissions of the filesystem that
> > you are mounting over /home (e.g. myfileserver:/export/homes).  Change
> > the permissions of /export/homes on myfileserver.
> 
> In my case, I haven't mounted anything at all yet. My map is an 
> executable, and since I haven't triggered an automatic mount (by 
> accessing /home/foo), the executable has not even been called once. 
> /home is empty.

And if you create a file inside /home before starting automount(8) it
will (not so) mysteriously disappear when automount is started.

Why don't you check what mounts you have after automount is started.

That may well answer your question and don't forget to check
if /etc/mtab is a symlink to a mount table in the proc file system.

If it isn't then the autofs file system mounts won't be present
in /etc/mtab but they will be seen in the mount table within the proc
pseudo file system at /proc/mounts.

Ian

--
To unsubscribe from this list: send the line "unsubscribe autofs" in

  reply	other threads:[~2015-09-14  9:52 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
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 [this message]
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=1442224340.3030.70.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=cbay@excellency.fr \
    --cc=frank.thommen@embl-heidelberg.de \
    /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.