All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: devnull@adc.idt.com
Cc: autofs@linux.kernel.org
Subject: Re: disable direct mounts
Date: Tue, 17 Nov 2009 14:30:01 +0800	[thread overview]
Message-ID: <4B0242E9.4050808@themaw.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0911170004530.26324@bos.adc.idt.com>

devnull@adc.idt.com wrote:
>>> We would like to continue to disable direct mounts. The other option is
>>> to use a different "auto.master" w/o the auto.direct, but we would like
>>> to avoid that.
>>
>> Why do you want to disable direct mounts?
> To solve our /usr/local issue.
> 
> Our NIS master is a Solaris box. We have an entry in auto.direct for
> /usr/local that currently points to our Sun Solaris binaries.
> The auto.direct is included in our auto.master
> 
> We are considering a move to autofs 5.x as part of our OS upgrade. We
> could create a separate auto.master.lnx that does not have auto.direct
> in it, but we prefer not to do that.
> 
> "Solving the /usr/local/ puzzle" as the NIS and NFS book suggests is
> something we can do, I am just not sure if we can do that right away.

That is probably the best solution.
You can use built in macros in the mount location of your maps to
achieve that. See autofs(5).

> 
> So someway to disable auto.direct would be useful for us.

You don't say if your maps are always from local files or some other source.

> 
> Thanks.

  reply	other threads:[~2009-11-17  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 17:10 disable direct mounts devnull
2009-11-17  1:20 ` Ian Kent
2009-11-17  5:12   ` devnull
2009-11-17  6:30     ` Ian Kent [this message]
2009-11-17  6:50     ` Ian Kent
2009-11-17 16:43       ` devnull
2009-11-18  1:30         ` Ian Kent

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=4B0242E9.4050808@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=devnull@adc.idt.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.