All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: David Meleedy <david.meleedy@analog.com>
Cc: autofs@linux.kernel.org
Subject: Re: /net support
Date: Sat, 28 Oct 2006 12:05:05 +0800	[thread overview]
Message-ID: <1162008305.3091.8.camel@localhost> (raw)
In-Reply-To: <200610272022.k9RKMVk5020007@jetcar.spd.analog.com>

On Fri, 2006-10-27 at 16:22 -0400, David Meleedy wrote:
> Are there any plans to implement this correctly?  We are seeing
> problems with the auto.net script that just loads up every
> directory provided by the machine.  For example some of our
> fileservers have a lot of mounts, and this can really start
> filling up the mount table.  Also, some fileservers let certain
> clients mount some of the directories provided but not others.
> The error messages are confusing our user's because they are
> trying to cd to:
> 
> /net/<machine_name>/foo
> and they see an error message about not being able to mount
> /net/<machine_name>/goo
> 
> It would be a lot cleaner if only the directory you are cd'ing
> to got mounted instead of every directory.

As Jeff says, autofs version 5 works in a similar way to other
automounters now, by mounting (and expiring) the exported shares as you
go.

There is also a built in "-hosts" map now.

However, I've recently discovered that I haven't covered some of the
export access control syntax used by Solaris servers so you may still
need to use the auto.net script.

This issue will never be fixed in version 4 because version 4 cannot
handle the nesting of mounts found in server export lists.

Ian

  parent reply	other threads:[~2006-10-28  4:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-27 20:22 /net support David Meleedy
2006-10-27 23:04 ` Jeff Moyer
2006-10-28  4:05 ` Ian Kent [this message]
2006-10-30 22:52   ` David Meleedy
2006-10-30 23:29     ` Jeff Moyer
2006-10-31  0:14       ` David Meleedy
2006-10-31  8:31         ` Ian Kent
2006-10-31 15:04           ` Jeff Moyer
2006-10-31 20:42           ` David Meleedy
2006-10-31 21:00             ` Joseph V Moss
2006-10-31 21:58               ` David Meleedy
2006-11-01  2:39             ` Ian Kent
2006-11-01 20:32               ` David Meleedy

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=1162008305.3091.8.camel@localhost \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=david.meleedy@analog.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.