All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Frank Thommen <frank.thommen@embl-heidelberg.de>
Cc: autofs@vger.kernel.org
Subject: Re: Using wildcards in multi-mount maps
Date: Mon, 01 Jun 2015 12:10:06 +0800	[thread overview]
Message-ID: <1433131806.2703.51.camel@pluto.fritz.box> (raw)
In-Reply-To: <1433131113.2703.43.camel@pluto.fritz.box>

On Mon, 2015-06-01 at 11:58 +0800, Ian Kent wrote:
> On Sun, 2015-05-31 at 20:05 +0200, Frank Thommen wrote:
> > Hi,
> > 
> > are wildcards within multi-mount maps supposed to work?
> 
> Good question.
> 
> > 
> > I have the following entry in our maps:
> > 
> > /etc/auto.master (local):
> >     /mymount yp:mymap --ghost
> > 
> > 
> > Indirect NIS map for /mymount:
> >     $ ypmatch webapps mymap
> >     /*         -timeo=30                   server:/local/exports/&
> 
> Yeah, that can't work.
> 
> The wildcard must be a single character at the start of the key, no
> other characters can be used.
> 
> So, no that can't be used in multi-mount map entries.
> 
> Keep in mind that for multi-mount map entries to work the offset paths
> must be known when the containing mount is performed so adding
> functionality like this isn't actually doable.
> 
> The substitution is based on replacing the whole key, autofs can't take
> part of a key and use it for substitution either.
> 
> What's more doing so would introduce the the need to handle multiple
> occurrences of the wildcard with matching of where to substitute each
> one and that isn't covered by the Sun map format AFAIK.
> 
> If this type of extended key pattern matching is really needed you could
> have a look at the amd map format. I haven't implemented the regex key
> matching functionality of am-utils in autofs but the variable length key
> matching combined with wildcard entries might be sufficient.

That probably should read "multiple component key matching" rather than
"variable length key matching".

> 
> Note that I also haven't implemented the am-utils multi-mount like map
> type either and the way they are specified in amd map format maps
> doesn't lend itself to this sort of wildcard handling either.
> 
> >     $
> > 
> > 
> > On the NIS server the map looks like this:
> >     webapps \
> >        /*         -timeo=30                   server:/local/exports/&

The other approach that might be useful is using submounts (Sun map
format) like:

webapps               -fstype=autofs autofs.wild

where autofs.wild could contain:
other-offset-submount             -fstype=autofs autofs.other-offsets
*          -timeo=30               server:/local/exports/&

and the map autofs.other-offsets is a subdirectory of lower level
mounts. Obviously you would need one of these for each sub directory of
mounts.

> > 
> > 
> > However on the client it looks like:
> > 
> >     $ ls /mymount/webapps
> >     *
> >     $ ls /mymount/webapps/user
> >     ls: /mymount/webapps/user: No such file or directory
> >     $
> > 
> > (/local/exports/user /is/ exported to this client from server)
> > 
> > This is on CentOS 5 with autofs 5.0.1.
> > 
> > Should that work or do I have to solve this mount config in an other way?
> > 
> > Frank
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe autofs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe autofs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2015-06-01  4:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 18:05 Using wildcards in multi-mount maps Frank Thommen
2015-06-01  3:58 ` Ian Kent
2015-06-01  4:10   ` Ian Kent [this message]
2015-06-06 18:02     ` Frank Thommen

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=1433131806.2703.51.camel@pluto.fritz.box \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=frank.thommen@embl-heidelberg.de \
    /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.