From: Ian Kent <raven@themaw.net>
To: giggzounet <giggzounet@gmail.com>
Cc: autofs@linux.kernel.org
Subject: Re: Automount /home for all the users when a user try to use /home
Date: Tue, 24 May 2011 11:23:06 +0800 [thread overview]
Message-ID: <1306207386.3398.6.camel@perseus.themaw.net> (raw)
In-Reply-To: <ir2fpp$6q3$1@dough.gmane.org>
On Thu, 2011-05-19 at 09:10 +0200, giggzounet wrote:
> Hi,
>
> I'm using autofs for years and on different configurations. It works
> great! so thx for your great work.
>
> But I have a little question/problem:
> We have a cluster (with CentOS 5.5). It's a little cluster, so the /home
> "is" on the master. And this /home is exported to the nodes. I have
> installed autofs in order to automount this /home when a user wants to
> use his /home.
>
> So at the moment the configuration is simple:
> cat auto.master
> /home /etc/auto.home
>
> cat auto.home
> * nfs_oscar:/home/&
>
>
> So when a user comes autofs mounts only the /home for the user.
>
> So at the moment it works. but I find it not optimal, because when 2
> users try to connect from a node I get 2 mounts.
>
> I would like to get this behaviour:
> when a user try to connect to his /home, autofs mount all the export
> /home. It is possible ?
It might be possible to come up with a method to mount all the keys in a
indirect map on first access but that sounds like it would be more
difficult than it's worth.
Do you really need to mount these separately?
Could you use a direct mount map instead?
You could do this by using the following:
in the master map (possibly /etc/auto.master):
/- /etc/auto.direct.homes
and /etc/auto.direct.homes could contain:
/home oscar:/home
This way there is only one mount not many and it will always make all
home directories available on first access.
Ian
next prev parent reply other threads:[~2011-05-24 3:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 7:10 Automount /home for all the users when a user try to use /home giggzounet
2011-05-24 3:23 ` Ian Kent [this message]
2011-05-24 6:32 ` giggzounet
2011-05-30 9:41 ` giggzounet
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=1306207386.3398.6.camel@perseus.themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=giggzounet@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 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.