All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Bill Shannon <bill.shannon@sun.com>
Cc: autofs@linux.kernel.org
Subject: Re: Ubuntu NFS automount problem
Date: Tue, 25 Nov 2008 02:43:52 +0900	[thread overview]
Message-ID: <1227548632.2913.33.camel@zeus.themaw.net> (raw)
In-Reply-To: <492ACF74.6000703@sun.com>

On Mon, 2008-11-24 at 07:59 -0800, Bill Shannon wrote:
> Bill Shannon wrote:
> >>> # cat /etc/auto.net
> >>> *    -rw,intr    &:/
> >>
> >> How is do you expect this to work, explain?
> 
> Ok, maybe the question you meant to ask is "how is the above entry
> supposed to achieve the effect you desire".
> 
> That's a good question.

And the answer is "it doesn't".
At least not on Solaris 9 or Linux.
I don't know about OpenSolaris or Solaris 10.

The reason I was confused is because of the internal contradictions in
you original two postings.

But, if you could have described the semantic rules which allowed that
apparent contradiction work the way you described then I would have been
happy to listen.

> 
> Going back to Solaris, I see that /net is handled by a special
> auto.master entry:
> 
> /net	-hosts	-nosuid
> 
> I'd forgotten all about that.
> 
> I just tried that on Linux with autofs and it doesn't seem to work.
> Is there a Linux equivalent for the "-hosts" pseudo-map on Solaris?

Yes, with autofs version 4 use "/net /etc/auto.net" in the master map
which generally should work the way you expect. The internal hosts map
is available in autofs version 5, which I suspect may be called autofs5
in ubuntu.

> 
> I'm having the same problem with the corresponding entry in my
> my auto.home map.  I guess exporting each individual home directory
> from zfs isn't going to work the same way exporting the entire /export/home
> directory works.  I guess I'll have to find a better way to handle that...

I don't know how zfs may change any of this either.

A wildcard map for an indirect map, which home directories usually are,
might be:

*	<home directory server>:/<home directory base directory>/&

  reply	other threads:[~2008-11-24 17:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23  2:27 Ubuntu NFS automount problem Bill Shannon
2008-11-24  4:08 ` Ian Kent
2008-11-24  7:25   ` Bill Shannon
2008-11-24 12:52     ` Ian Kent
2008-11-24 15:42       ` Bill Shannon
2008-11-24 16:00       ` Peter Staubach
2008-11-24 16:26         ` Ian Kent
2008-11-24 20:31         ` Bill Shannon
2008-11-25  1:32           ` Ian Kent
2008-11-25 10:27             ` Ondrej Valousek
2008-11-25 11:27               ` Ian Kent
2008-11-25 11:44                 ` Ondrej Valousek
2008-11-25 12:11                   ` Ian Kent
2008-11-24 15:59     ` Bill Shannon
2008-11-24 17:43       ` Ian Kent [this message]
2008-11-24 20:35         ` Bill Shannon
2008-11-25  1:21           ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2008-11-25  1:10 Brent Callaghan

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=1227548632.2913.33.camel@zeus.themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=bill.shannon@sun.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.