From: "Douglas E. Engert" <deengert@anl.gov>
To: "Francesco P. Lovergine" <f.lovergine@ba.issia.cnr.it>
Cc: autofs@linux.kernel.org
Subject: Re: Looking for a per user submount...
Date: Tue, 29 Jan 2008 08:27:09 -0600 [thread overview]
Message-ID: <479F37BD.3050900@anl.gov> (raw)
In-Reply-To: <1201570926.3072.17.camel@raven.themaw.net>
Ian Kent wrote:
> On Mon, 2008-01-28 at 11:11 +0100, Francesco P. Lovergine wrote:
>> I was looking for some sort of automounting for per-user subtrees.
>> Essentially I need to bind-mount on demand some per user (users are sql-based)
>> subdir like /path/<user>/mount_point, where /path/<user> is a true dir.
>> I'm missing something or it cannot be performed using autofs without
>> adding each entry explicitly for every users ?
Have you looked at using an executable map? Something like in the master map:
/topdir program:/etc/auto_per_user
/etc/auto_per_user:
#!/bin/sh
# $1 is <user>
echo ":/path/$1/mount_point"
>
> Try something like.
>
> In the master map:
> /topdir /etc/auto.users
>
> In auto.users:
> * :/path/&
>
> Clearly, the automount entries for future mounts aren't known until they
> are triggered, so they can't be seen no matter what options you use.
>
> Ian
>
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
>
>
--
Douglas E. Engert <DEEngert@anl.gov>
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
next prev parent reply other threads:[~2008-01-29 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 10:11 Looking for a per user submount Francesco P. Lovergine
2008-01-29 1:42 ` Ian Kent
2008-01-29 14:27 ` Douglas E. Engert [this message]
2008-01-29 14:33 ` Francesco Paolo Lovergine
2008-01-29 15:23 ` Douglas E. Engert
2008-02-04 15:57 ` Jeff Moyer
2008-01-29 15:26 ` Stef Bon
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=479F37BD.3050900@anl.gov \
--to=deengert@anl.gov \
--cc=autofs@linux.kernel.org \
--cc=f.lovergine@ba.issia.cnr.it \
/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.